CPA: calls for a period

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

Annotations already indicate read-only, idempotent. Description adds pagination behavior, cost-free operation, rate limit, and the fact that it queries by startTime. These are useful behavioral details beyond 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 sentences, around 80 words, front-loaded with purpose. No redundant or unnecessary 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 pagination, rate limit, use case, and follow-up tools. Lacks explicit ordering of results (ascending/descending by startTime), but overall sufficient given annotations and 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?

Schema describes parameters with 100% coverage (dateTimeFrom, limit, offset). Description does not elaborate on parameter details. Baseline 3 is appropriate as schema handles param semantics.

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 it returns a paginated list of CPA calls by startTime. Explicitly mentions version (v2) and distinguishes from sibling tools by noting returned IDs are suitable for cpa_get_call_by_id_v2 or filing a complaint.

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?

Tells the agent to use the tool to iterate over calls for a period and provides follow-up actions. Mentions rate limit (1 req/min). Does not explicitly state when not to use or compare with other list tools, but context is clear for the CPA domain.

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