Repository inventory

ken-cavanagh-glean/fieldkit

Skills indexed from this repository, with install-style signals scoped to the repo.
6 skills18 GitHub stars0 weekly installsPythonGitHubOwner profile

Overview

This skill helps you design and optimize tools that language-model agents use to interact with systems. It focuses on clear tool contracts, consolidation versus separation, and response/error formats that enable reliable agent behavior. Use it to create tool descriptions, reduce ambiguity, and choose when to simplify or consolidate tool sets.

How this skill works

The skill inspects tool APIs and descriptions to ensure they answer what the tool does, when to use it, what inputs it accepts, and what it returns. It evaluates naming, defaults, response verbosity options, error messages, and namespacing to reduce agent confusion and context usage. It can recommend consolidation or architectural reduction when appropriate and propose improved description text and examples for agent consumption.

When to use it

  • Creating new tools or APIs intended for use by language-model agents
  • Debugging repeated tool-selection or misuse failures in agent runs
  • Optimizing an existing tool collection to reduce ambiguity and tokens
  • Deciding whether to consolidate multiple narrow tools into a single comprehensive tool
  • Evaluating third-party tools for safe and effective agent integration

Best practices

  • Write descriptions that explicitly state what the tool does, when to use it, inputs (types and defaults), and expected outputs
  • Prefer consolidated tools for end-to-end workflows unless behaviors are fundamentally different
  • Provide concise and detailed response formats and let agents choose verbosity
  • Design actionable error messages that include how to recover or correct inputs
  • Use consistent naming conventions (verb-noun) and parameter names across tools
  • Limit tool count (rough guideline: 10–20) and use namespacing to organize larger sets

Example use cases

  • Replace several narrow CRUD endpoints with a single scheduling tool that handles discovery and creation
  • Convert vague database search tools into a well-typed get_customer(customer_id, format) with clear errors
  • Audit a tool collection to remove overlapping functionality and reduce agent selection errors
  • Implement concise/detailed response options to control token usage in multi-step reasoning
  • Use an agent to analyze failure logs and iteratively improve tool descriptions and defaults

FAQ

Keep tools separate when they have fundamentally different behaviors, are used in distinct contexts, or must be called independently. Consolidation is for reducing ambiguity, not forcing unrelated features together.

How many tools are too many?

Research suggests 10–20 tools is reasonable for many applications. If you need more, use namespacing, umbrella routing tools, or group related functions under comprehensive interfaces.

6 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational