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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds "Paged", a genuine behavioral trait, but the schema already documents page/per_page and next_page semantics, so the added value is thin. Nothing about result size caps, ordering defaults (beyond schema) or empty-result behavior is disclosed.

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 tight sentences: the first front-loads the resource, the filter dimensions and the enum values, the second tacks on pagination in a single word. No filler or restatement of the title.

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?

For a read-only, 14-optional-parameter list tool with full schema coverage and a pagination-safe readOnly hint, the description covers purpose, filters and paging adequately. The only mild gap is that with no output schema, nothing is said about the shape of returned confirmations (id/number fields needed for follow-up calls), though that is a minor omission for a list endpoint.

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 100% with per-parameter descriptions and formats, so the baseline is 3. The description's summary of filter dimensions (client, status, number, date range, text) mirrors what the schema already states and adds no syntax, default, or combination rules beyond it.

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?

Names a specific verb and resource ("List order confirmations") and even supplies the German domain synonym (Auftragsbestaetigungen), which helps disambiguate in a German accounting toolset. It is clearly separable from the singular sibling billomat_get_confirmation and from billomat_list_offers/invoices by the resource noun.

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 filter enumeration (client, status, number, date range, text) implies the contexts in which this tool is appropriate, but there is no explicit when-to-use statement, no guidance on when to prefer billomat_list_offers or billomat_get_confirmation instead, and no note that all filters are optional.

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