search_schema

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

No annotations provided; description discloses that it returns a short, ranked list. However, it does not address authentication, rate limits, or other behavioral traits beyond the output format.

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?

Two paragraphs are focused and front-loaded. First sentence states purpose and output, second explains the argument. No unnecessary words.

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 simple tool with one parameter and no output schema, the description covers main use case and output format. Could add details on case-sensitivity or limits, but is adequate for selection.

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 has 0% description coverage, but description compensates by explaining the 'keyword' parameter accepts one or more keywords and provides examples. Adds significant meaning beyond type string.

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?

Clearly states it searches for a keyword across dimensions and metrics and returns a ranked list. Distinguishes from sibling tools that categorize or retrieve data.

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?

Explicitly says it's the most efficient way to discover fields for a query, guiding when to use. Could mention alternatives but provides sufficient context.

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