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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context by listing the campaign status values and clarifying that lifecycle actions stay in the panel, though it omits pagination behavior and response shape.

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 short and front-loaded: it starts with read/resource scope, then gives status values, then notes out-of-scope lifecycle actions. Every clause carries useful information with no filler.

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?

With no output schema and no schema parameter descriptions, more detail about pagination and what a campaign record contains would help. It is adequate for selecting the tool and understanding the status filter, but incomplete for correct pagination and return expectations.

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 supplies the allowed voip_campaign_status values, which the schema does not enumerate, but page and per_page remain undocumented and filtering behavior is only implied.

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 the resource as 'Outgoing campaigns' and tags it '[read]', so the operation and scope are clear. It also explicitly excludes start/pause/cancel actions, though it does not distinguish listing from get_voip_campaign or list_voip_calls.

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?

It implies this tool is for reading outgoing campaigns and says starting, pausing, and cancelling happen elsewhere. However, it gives no positive guidance on when to use this versus get_voip_campaign or list_voip_calls, nor how to use the status filter.

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