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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are newest-first, pagination is cursor-based, and text search is unsupported — the last point prevents a plausible misuse.

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 short sentences, zero filler, with the core behavior front-loaded and the API limitation appended as a caveat. Every clause carries information.

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?

There is no output schema, so the description must carry return-value context; it hints at 'coverage' and a cursor but never explains what coverage means or what the page envelope looks like. With 5 parameters, 2 required, and low schema coverage, the definition is usable but leaves real gaps for correct invocation.

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 only 40%: limit, cursor and status carry no descriptions, and only company/environment are documented. The description mentions the cursor exists but adds no meaning for limit, status values, or cursor format, so it fails to compensate for the coverage gap.

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 (company-owned cases/conversations), plus ordering (newest first) and return shape hints (coverage, cursor). It is distinguishable from summer_cases_get and summer_messenger_conversations_assistant, though the phrase 'cases or conversations' leaves some ambiguity about which entity is actually returned.

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?

No when-to-use guidance and no named alternative among the many sibling list tools (e.g. summer_events_list, summer_investigations_list). The only constraint given is a negative one — 'Text search is not available through the API yet' — which tells the agent what cannot be done but not when this tool is the right choice.

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