listPhoneNumbers

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the read-only nature is disclosed. The description adds account scoping but does not mention pagination behavior or response format, going slightly beyond annotations but not richly.

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?

The description is a single clear sentence with a minimal tag suffix. It is front-loaded with the purpose and contains no redundant content.

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 paginated list tool with strong annotations and full schema coverage, the description provides sufficient context to select and invoke the tool. Minor gap: no mention of response shape, but no output schema exists and the behavior is straightforward.

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?

Both pageno and pagesize have detailed schema descriptions with defaults and ranges, achieving 100% schema description coverage. The description adds no parameter-specific information beyond the schema, so 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?

Description uses a specific verb 'Retrieve' and resource 'all phone numbers associated with your account', clearly distinguishing it from sibling operations like attach, detach, or import phone numbers.

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?

Usage is implied by the phrase 'Retrieve all phone numbers associated with your account', but there is no explicit when-to-use guidance or comparison with alternatives like listKnowledgeBaseFiles or detachPhoneNumber.

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