search_tools

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

No annotations provided, so description carries full burden. Only states 'search for available tools by keyword', omitting details like search mechanics, result format, or constraints. Insufficient for an agent to understand exact 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?

Single, front-loaded sentence efficiently conveys purpose. 'Vitally' is unnecessary but not distracting. No fluff, but could be more informative without lengthening.

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?

Tool is simple but lacks output details crucial for an agent: no output schema, description doesn't specify return format (tool names, full definitions, match criteria). Incomplete for effective invocation.

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?

Input schema fully describes 'keyword' parameter (100% coverage). Description echoes purpose without adding new semantics (e.g., format, case sensitivity). Meets baseline but adds no extra value.

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?

Description clearly states action 'search' and resource 'available tools' with qualifier 'by keyword'. Distinguishes from sibling tools which are domain-specific (accounts, conversations, notes) by being a meta-tool for tool discovery.

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?

No explicit guidance on when to use versus alternatives, but the unique meta-purpose makes alternatives irrelevant. Lacks direction on search behavior (case sensitivity, match type).

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