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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint and the set of case fields; it says nothing about pagination behavior, result caps, or default page size beyond what the schema already states.

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?

A single tight sentence plus the endpoint reference, front-loaded with the verb. Nothing is wasted, though the trailing 'GET /cases/' conveys little to an agent that already has the tool.

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 100% schema coverage and safety annotations, the description covers purpose, resource scope and filterable subject matter. Response shape is the only real gap, and a list endpoint's return form is largely implied.

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 the schema fully documents sort, limit, start and the filter object. The description's field list (title, close date, assigned users, deal, company) marginally extends the schema's generic examples by naming case-specific fields, but adds no operator or format guidance.

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 clear verb+resource ('List or search cases') and disambiguates the resource as 'support or project cases', listing the fields that characterize a case. It is distinguishable from cogmento_get_case by the list/search framing, though it never names that sibling.

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?

'List or search cases' implies when to reach for it (browsing or filtering the case collection), but there is no explicit when-not, no mention of when to prefer cogmento_get_case or cogmento_create_case, and no guidance on when to use filters vs. sort.

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