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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds that results are a 'bounded page' and filtered to one currency, which is useful context beyond annotations. However, it does not describe pagination ordering, maximum limits, or return contents, so it remains only moderately transparent.

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 a single, front-loaded sentence with no filler. Every phrase contributes to scope or filtering, making it appropriately 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?

The tool has six nested parameters, no parameter descriptions, and no output schema. A one-sentence description does not provide enough guidance for correct invocation, particularly for 'value' and 'months', nor does it explain what a page of invoices contains.

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 description coverage is 0% for six nested parameters. The description partially maps dimension and currency and hints at pagination through 'bounded page', but it leaves key parameters such as 'value' and 'months' undefined. With low schema coverage, more parameter meaning should have been supplied.

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 states a specific verb and resource: 'Read a bounded page of invoices contributing to a month, vendor or category in one currency.' This clearly distinguishes the tool as an invoice-level drill-down rather than a transactional operation. It does not explicitly contrast itself with siblings like get_spend_summary or search_invoices, so it falls short of the top score.

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 implies usage for inspecting invoices behind a month/vendor/category spend figure, but it never says when to choose this over get_spend_summary, search_invoices, or get_invoice. No explicit alternatives or exclusions are provided.

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