intelx_phonebook_results

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

No annotations are provided, so the description carries the full burden. It discloses the prerequisite API key and the sequential dependency, but does not mention pagination, error handling, or return format beyond what the schema implies. For a simple retrieval operation, this is adequate but not rich.

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 short sentences immediately state the action and the usage prerequisite. No filler or redundant wording; every word earns its place.

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 straightforward retrieval tool with 3 parameters and no output schema, the description provides the core essentials: purpose, sequence, and prerequisite. It lacks a note about response format, but the phrase 'phonebook search results' sufficiently implies the return type. Complete enough for a knowledgeable agent.

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 100%, with each parameter already well-described ('Phonebook search ID from intelx_phonebook', 'Max results per page', 'Result offset'). The description adds no extra semantic meaning beyond the schema, so the baseline 3 applies.

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 a specific verb ('Retrieve') and resource ('phonebook search results from IntelligenceX by ID'), clearly distinguishing it from the sibling tool intelx_phonebook. The phrase 'by ID' and the context of result retrieval make its 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 'Use after intelx_phonebook', providing a direct sequential instruction. Also notes the prerequisite 'Requires INTELX_API_KEY'. This gives clear when-to-use guidance and differentiates from the search initiation tool.

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