cloudflare_list_invoices

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

Annotations only indicate readOnlyHint, idempotentHint, and destructiveHint. The description adds substantial behavioral context: it uses a deprecated Cloudflare API endpoint, automatically converts USD to EUR using ECB rates via Frankfurter API, and lists each returned field. This fully informs an agent of side effects and data transformations.

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 concise at 12 lines, front-loaded with the core purpose, and structured with a bulleted list of returned fields. Every sentence adds value—no redundancy or tautology. This is an efficient, well-organized description.

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?

Given the tool's low complexity, detailed annotations, and presence of an output schema, the description is complete. It covers the main behavior (listing invoices), conversion logic, returned fields, token requirement, and endpoint deprecation. No gaps for an agent to operate correctly.

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?

With 0% schema description coverage, the description must explain parameters. It clearly explains the convert_to_eur parameter (default behavior, conversion source). However, it provides no explanation for page and per_page parameters beyond what the schema names imply. Pagination details are missing, so the description only partially compensates.

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 starts with 'List billing history from Cloudflare', a specific verb and resource. It clearly distinguishes from sibling tools like cloudflare_get_invoice and cloudflare_get_latest_invoice by indicating it lists all invoices. The summary of returned fields further clarifies the tool's scope.

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 states when to use the tool (list billing history) and includes prerequisites (CLOUDFLARE_API_TOKEN). It does not explicitly state when not to use or compare with alternatives, but the sibling tool names provide implicit guidance. Lack of explicit exclusions prevents a higher score.

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