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

Annotations already declare readOnly/idempotent/closed-world/non-destructive, so safety is covered. The description adds value beyond them by disclosing the result ordering (newest first) and the fields returned, though it says nothing about pagination defaults or result-size limits.

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-loaded with the read marker and resource, then the returned fields and ordering. No filler; the trailing sentence about import_voip_campaign_targets earns its place by framing the object's purpose.

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 read-only list tool with strong annotations and no output schema, naming the returned fields and ordering is exactly what the description needs to supply. The remaining gap is pagination, which is neither in the description nor the schema.

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 parameters (page, per_page) have 0% schema description coverage and the description never mentions them. The agent is left to guess that the listing is paginated and what per_page does, which is a real gap for the only two inputs.

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?

"[read] Saved call lists" states a specific verb and resource, and enumerates the returned fields (name, description, calling code, number of people) plus ordering (newest first). That distinguishes it from sibling list_voip_list_members / list_voip_campaigns by implication, though no sibling is named explicitly.

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?

The link to import_voip_campaign_targets hints at the downstream workflow (add a whole list to a campaign), which implies these are reusable recipient lists. However there is no explicit when-to-use / when-not guidance versus list_voip_list_members or the other VOIP list tools, so the agent must infer selection.

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