Agent Farm

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'parallel' processing and 'optionally synthesize,' hinting at concurrency and output merging, but fails to detail critical aspects like rate limits, error handling, authentication needs, or what 'synthesize' entails (e.g., aggregation, summarization). This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose. The examples are concise and relevant, though the structure could be slightly improved by separating usage notes from examples. Overall, it avoids unnecessary verbosity and earns its place with efficient sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (parallel querying with synthesis), no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on output format, error conditions, performance implications, and how synthesis integrates with results, making it inadequate for an agent to use the tool effectively without guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It explains 'queries' as a 'JSON array of query strings OR single topic to auto-expand' with examples, adding meaning beyond the schema's basic string type. However, it doesn't clarify the 'synthesize' parameter's effect or default behavior, leaving half the parameters inadequately explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Query KMKB from multiple angles in parallel, optionally synthesize,' which provides a general purpose (querying KMKB with parallel processing and optional synthesis). However, it lacks specificity about what KMKB is (a knowledge base, database, etc.) and doesn't clearly differentiate from sibling tools like 'api_swarm' or 'synthesize,' making it vague rather than distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes examples of query formats (JSON array or single topic) but offers no guidance on when to use this tool versus alternatives like 'synthesize' or other swarm tools. It implies usage for parallel querying but doesn't specify contexts, prerequisites, or exclusions, leaving the agent with minimal direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.