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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds real context beyond that — the 250-row page cap and the exact field set returned — but says nothing about authentication, rate limits, or what happens on an empty result set.

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?

Three short sentences, zero waste, front-loaded with the action and resource before the return fields and the paging limit. Nothing is repeated verbatim from structured data.

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 list tool with full schema coverage and no output schema, the description covers the action, the returned fields, filtering, paging and ordering. What remains missing is sibling disambiguation, which matters here because invoice_lines sits adjacent in the tool list.

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% and each parameter is documented in the schema, so baseline would be 3. The description restates the 250 cap and the filter/ordering capability in prose, giving the agent the operative constraint at a glance without opening the schema, which is a modest but genuine addition.

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 and resource ('List invoices in Gripp') and enumerates the returned fields (number, date, status, company, totals, amount paid, open amount), so the agent knows exactly what it gets. It does not explicitly differentiate itself from the closest sibling, gripp_list_invoice_lines, leaving that distinction to inference from the resource name.

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?

Usage is implied by the name and the mention of filters/paging/ordering, but the description never says when to prefer this over gripp_list_invoice_lines or gripp_get_record, nor any prerequisites. The agent must infer the routing decision.

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