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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds the sort order ('newest-updated first') and the underlying GET endpoint, which is genuinely useful context, but says nothing about result counts or expansion behavior beyond what the schema's include parameter already covers.

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 sentences, no filler, with the resource and scope front-loaded before the endpoint reference. Every clause earns its place.

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 simple read-only list tool with full schema coverage and an annotation declaring read safety, the description supplies scope, ordering, and endpoint. Only minor gaps remain (return envelope/pagination shape), and with no output schema that is a small omission.

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%: limit, offset, include, and organization_id are all documented in the schema, including defaults and the '*' expansion option. The description adds no parameter-level detail, 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?

States a specific verb ('List') and resource ('cases (conversations)') with an explicit scope: 'raised by members of one organization'. The scope does distinguish it in practice from kayako_list_cases, but the sibling is never named, so the separation is inferred rather than stated.

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 organizational scoping implies when this tool is appropriate (you know the org id and want its cases), but there is no explicit when-to-use, when-not-to-use, or pointer to kayako_list_cases / kayako_search for cross-org or filtered queries. Usage is only implied.

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