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

No annotations provided, so description carries full burden. It describes the tool as a search returning specific fields, with no side effects. Mentions free, no auth, unlimited searches. Lacks info on latency or rate limits, but overall clear and honest.

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?

Four sentences, no redundancy. Each sentence adds distinct value: purpose, return fields, use case, and constraints. Front-loaded with key action ('Search the Zambo Agent Registry').

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 search tool with no output schema, the description covers all essential aspects: what it does, what it returns, how to use it, and how it integrates with other tools (axis_tool_dispatch). Nothing missing.

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%, but description adds value by explaining query types (name, keyword, capability) with concrete examples (e.g., 'web scraping'). Reinforces the purpose of limit and capability parameters. Slightly above baseline.

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 clearly states it searches a registry of AI agents by capability/name/description, returning specific fields. It distinguishes itself from siblings by mentioning routing via axis_tool_dispatch, and the context of public phone book makes purpose unambiguous.

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 when to use: 'discover agents that can perform specific tasks'. Mentions alternative action (connect directly or route payments via axis_tool_dispatch). Also notes it's free, no auth, unlimited searches, providing clear usage constraints.

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