Get one WA phone number — quality rating / messaging tier

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

No annotations. Description specifies returned fields but does not explicitly state read-only nature or any behavioral constraints. Adequate for a simple GET.

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?

Extremely concise, front-loaded with path and key fields. No wasted words, but could be better structured with parameter explanations.

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?

No output schema, so description partially compensates by listing returned fields. Missing details on error handling or optional parameters like 'fields'.

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 0%. Description only mentions phone_number_id via path, and does not explain parameters like 'fields' array. Fails to add meaning beyond schema.

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 verb (GET), resource (phone number), and specific returned fields. Title reinforces singular retrieval, distinguishing it from wa_phone_numbers list.

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 when/alternatives guidance, but sibling tool wa_phone_numbers implies this is for single phone number, making usage clear implicitly.

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