⚠️ CPA: complaint about a call

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

Adds behavioral context beyond annotations: irreversible record, rate limit, requirement for callId from preceding call. Annotations indicate destructiveHint=true and readOnlyHint=false, which aligns with the description's emphasis on irreversibility.

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 sentences with no wasted words. Front-loaded with warning emoji and main action. Every sentence adds unique 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?

Covers purpose, usage, prerequisites, and constraints. Lacks return value description, but since there's no output schema, this is a minor gap. Otherwise complete for a mutating action.

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 coverage is 100%, so description doesn't need to detail parameters but adds value by explaining callId must come from a specific preceding call. This provides useful context beyond schema descriptions.

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?

Clearly states 'Files a complaint about a CPA call by its callId' and differentiates from sibling tool 'cpa_create_complaint_by_action_id' which handles both calls and chats. Uses specific verb and resource.

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?

Explicitly states when to use (disputing charge), prerequisite (callId from cpa_get_calls_by_time_v2), alternative for both calls and chats, and rate limit of 1 request/min. Irreversible nature also guides usage.

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