cloudflare_get_latest_invoice

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

Adds value beyond readOnlyHint annotation by detailing currency conversion behavior and return fields (amount, currency, amount_eur, etc.). No contradictions with 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?

Well-structured with clear front-loading of purpose. Each sentence adds value, though slightly verbose with return field listing; could be more concise.

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?

Despite missing output schema in input, description explicitly lists return fields. Annotations cover safety. Guidelines and parameter semantics are complete for this tool's complexity.

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?

While schema already has description for convert_to_eur, the tool description adds context about historical exchange rates and shows how parameter affects output (amount_eur, exchange_rate). Schema coverage is actually present despite context signal claiming 0%.

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 'Get the most recent Cloudflare billing item' and specifies verb and resource. It distinguishes from siblings like cloudflare_get_invoice and cloudflare_list_invoices by focusing on the latest item.

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?

Provides context for automated monthly bookkeeping and suggests using oc_create_expense next. Mentions requirement for CLOUDFLARE_API_TOKEN. Does not explicitly say when not to use or compare with alternatives.

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