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

Annotations indicate it is a non-read-only, idempotent, non-destructive action. The description adds behavior detail: 'Distribution resumes from where it left off.' This is helpful but does not disclose potential side effects. Adequate given annotations.

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?

Three concise sentences: action, behavior detail, precondition. No unnecessary words. Efficiently communicates essential information.

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 mutation with one parameter and no output schema, the description covers the action, precondition, and resumption behavior. It does not explain error cases or return values, but given the simplicity, it is largely complete.

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?

The sole parameter 'adRequestId' is fully described in the input schema (100% coverage). The tool description does not add extra semantics beyond the schema, so baseline score of 3 applies.

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 clearly states the verb 'Resume' and the resource 'paused ad request campaign'. It distinguishes from sibling tools like 'pause_ad_request' and 'stop_ad_request' by specifying the precondition that only paused ad requests can be resumed.

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 description explicitly states the condition for use: 'Only paused ad requests can be resumed.' It implies when to use but does not explicitly mention alternatives or when not to use (e.g., if already running). Still provides clear context.

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