get_case_memory

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

No annotations are provided, so the description carries the full burden. It does add one meaningful behavioral fact beyond the schema: only *approved* drafts are returned, implying unapproved ones are filtered out. It says nothing about ordering, pagination, or how the limit truncates results, which is a notable omission for a read tool with no annotation coverage.

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 front-loaded sentence with no filler; the resource and scope appear before the purpose. It is efficient, though arguably too terse given the documentation gaps it leaves behind.

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?

An output schema exists, so return-value explanation is not required. However, with zero schema coverage, no annotations, and an undefined `limit` default of 2, the description is too thin for an agent to know what it will receive or how results are bounded.

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 0% across three parameters. The phrase 'instance/request pair' loosely maps to instance_id and request_id, but the `limit` parameter (with default 2) is never explained in either the schema or the description, so the description 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 (read) and resource (approved drafts) scoped to an instance/request pair, with the intent (historical context) made explicit. It is distinguishable from siblings like get_instance_summary or get_timeline by the 'approved drafts' resource, though it never names an alternative directly.

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?

'as historical context' implies the situation that motivates the call (looking for precedent), but there is no explicit when-to-use, when-not-to-use, or guidance on choosing this over get_instance_summary/get_timeline. Usage is implied rather than stated.

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