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

Annotations already declare readOnlyHint=true, so safety is covered and the description's job is to add operational context. It does note the 250-per-call ceiling, but that is already in the schema; the genuinely new bit is the underlying API call (offer.get) which aids debugging but says nothing about the response envelope or how to page past 250. Adequate but thin for a read-list tool with no output schema.

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, front-loaded with the resource and what it returns, then capabilities, then the API endpoint. The trailing "Gripp API: offer.get" is developer-facing trivia rather than agent guidance, but it is a minor cost against an otherwise tight structure.

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 zero-required-parameter, read-only list tool with no output schema, the description does the important remaining work: naming the returned fields so the agent knows the row shape and stating the page-size ceiling. It stops short of explaining pagination behavior (e.g. whether a total count is returned, how to iterate past 250), which is the one genuine gap.

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 filter syntax, operator list, default sort and offset paging are all fully documented in the schema. The description only echoes the max-250 cap and adds no field names, filterable-field hints, or sorting caveats beyond what the schema provides, so the 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?

Specific verb + resource ("List offers in Gripp") and it usefully disambiguates the domain term by equating offers with quotes and enumerating the fields each row carries (number, name, date, phase, company, totals, acceptance status). It does not explicitly differentiate itself from entity-listing siblings like gripp_list_invoices, but the entity boundary is clear from the 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?

"Supports filters, paging (max 250 per call) and ordering" only implies usage: it tells you the tool is a filtered list but not when to pick it over alternatives or what it cannot do. There is no explicit exclusion, no prerequisite, and no guidance on when a single-record fetch (gripp_get_record) would be more appropriate.

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