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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful detail that a campaign object includes status and spend so far, but says nothing about freshness of the spend figure, whether missing campaigns error or return empty, or auth/scope requirements.

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?

A single short sentence that front-loads the resource and lists the returned facets with no filler. Nothing redundant or out of order.

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 only two parameters and no output schema, the description partially compensates by naming the fields returned (configuration, status, spend). However, for a getter sitting among several dialer read tools, it does not do enough to establish how its payload differs from get_dialer_report or list_dialer_campaigns.

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 100%, so campaign_id ("campaign UUID") and the purpose field are already documented and the baseline is 3. The description adds no further meaning about identifier format or how the purpose string affects the call.

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 names a specific resource (one dialer campaign) and enumerates what it returns: configuration, status, and spend so far. The singular "One" implicitly contrasts with list_dialer_campaigns, but the sibling is never named, so the agent must infer the distinction.

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: the singular framing suggests fetching a single campaign when its ID is known. There is no explicit guidance on when to prefer this over list_dialer_campaigns, get_dialer_report, or get_dialer_live, and no stated prerequisites or error conditions for an unknown campaign_id.

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