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

Annotations already cover the safety profile (readOnlyHint=true), so the description's job is to add context — and it does: it discloses sort order, a hard cap of 100, and that truncation is signaled in the reply. It stops short of saying how to retrieve results beyond the cap, which is the one behavioral gap.

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 carries scope, ordering, cap and truncation semantics; the second carries return fields and the underlying endpoint. Nothing is redundant and the key constraints are front-loaded.

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 one-parameter read-only list tool with no output schema, this covers ordering, cap, truncation signaling, returned fields and the endpoint. The remaining gap is the absence of any guidance on paginating past the 100-item cutoff, which matters given the description explicitly raises that case.

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?

There is a single parameter with 100% schema description coverage, including where to obtain its value, so the schema does the work. The description adds no format or sourcing detail beyond what the schema already states; 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?

The description names a specific verb and resource (list conversations of one customer) and adds scope details — oldest first, at most 100 — that let an agent distinguish it from gladly_get_conversation and gladly_list_conversation_items without opening either schema.

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 single-customer scope and the schema note that customer_id comes from gladly_find_customers, which sketches a workflow. But the description never states when to prefer this over gladly_get_conversation or gladly_list_conversation_items, nor any preconditions or exclusions.

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