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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context—ordering, included fields, and filter semantics—but omits pagination behavior despite page/per_page parameters, leaving a gap.

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 two sentences, front-loaded with the core behavior and followed by parameter details. It is dense but every clause (ordering, fields, filter forms, enum values) adds information an agent needs.

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 read-only list tool with no output schema and eight parameters, the description covers the operation, result ordering, returned fields, and the non-obvious filter/enum semantics. It lacks pagination details and explicit routing against get_voip_call, but is otherwise sufficient.

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%, so the description must compensate. It explains that the assistant and number filters accept an id or uuid and supplies the exact allowed values for voip_call_status and voip_call_direction, which the schema does not. Page/per_page are conventional and left implicit, but the ambiguous parameters are covered.

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 (list) and resource (VOIP calls) plus ordering ('newest first') and returned fields ('summary and topic'), making the operation clear. It does not explicitly differentiate from siblings like get_voip_call or list_voip_campaigns, so it stops short of a 5.

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 only implied by the verb 'list'; the description never states when to use this tool versus get_voip_call for a single call or the other list_voip_* endpoints. No exclusions, prerequisites, or alternative routing are provided.

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