search-tools

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

Without annotations, the description states it 'returns matching tool names + descriptions across all categories', which transparently describes the output. It does not disclose safety (read-only) but the search nature implies no side effects.

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 sentences with no redundancy. The purpose is front-loaded and every sentence adds value: first states purpose, second gives usage guidance.

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?

For a simple discovery tool with 3 params and no output schema, the description sufficiently explains return format (tool names + descriptions) and usage pattern. No gaps remain.

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 coverage is 100% and parameter descriptions are clear. The tool description adds minimal extra meaning beyond the schema (e.g., 'natural language query' mirrors schema). Baseline 3 is appropriate.

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 uses the verb 'discover' and specifies the resource 'available tools' via natural language query. It distinguishes itself from sibling search tools like 'search-metadata' by focusing on tool discovery rather than data asset search.

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 instructs the agent to 'call this first, then call the specific tool you need.' This provides clear when-to-use guidance and implies alternatives (specific tools) to call after discovery.

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