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', signaling pagination, which is useful behavior beyond the annotations. It does not mention default ordering, result caps, or auth/scope requirements.

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 compact sentences; the filter list is front-loaded and 'Paged' is a tight trailing signal. Slightly list-heavy but no filler.

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?

A read-only list tool with full schema coverage and an annotation covering safety is minimally complete enough to call. It lacks usage routing to siblings and any indication of return shape beyond 'Paged', which is adequate but leaves gaps for an agent choosing among list tools.

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%, so every parameter is already documented with format and range. The description restates the filter categories (client, status, number, date range, text) but adds no syntax beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (List) and resource (offers/Angebote) with a clear enumeration of filter dimensions. The parenthetical German synonym disambiguates within a sibling set that also contains billomat_list_invoices and billomat_list_confirmations.

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?

No explicit when-to-use guidance: it doesn't say to prefer billomat_get_offer for a single record, nor when to reach for this vs. a different list tool. The filter enumeration implies it is a filtered browse, but no alternative or precondition is named.

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