intelx_phonebook_results

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

Annotations already declare readOnlyHint and openWorldHint. The description adds the prerequisite tool and auth requirement (INTELX_API_KEY), which annotations do not convey. Return format is undocumented but no output schema exists, so this is a meaningful addition.

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 compact sentences front-load the action, then give the prerequisite and auth requirement. No waste.

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?

Covers the dependency, auth, and identification requirements for a simple read retrieval tool with no output schema and full param coverage. Pagination behavior for limit/offset is left to the schema, which is adequate but slightly thin.

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%, so id, limit, and offset are already fully documented. The description adds no format or paging semantics beyond what the schema provides, making baseline 3 correct.

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?

States a specific verb (Retrieve) and resource (phonebook search results) plus the source (IntelligenceX) and the keying parameter (by ID). It names the sibling it depends on, distinguishing it from intelx_phonebook and intelx_search_results.

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 tells the agent to use it after intelx_phonebook, giving clear sequencing. It does not name when NOT to use it or contrast with intelx_search_results, but the dependency condition is unambiguous.

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