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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds that it returns a 'free summary' and 'every finding in detail once the case has been unlocked,' which is useful context about output content and the lock state dependency. However, it doesn't explain what 'unlocked' means or how to achieve it, leaving a 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 concise sentences, front-loaded with the action, no wasted words.

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?

With no output schema and minimal annotations beyond safety, the description should explain more about the return value and the 'unlocked' state. It mentions a summary and findings but doesn't detail the distinction or prerequisites, leaving an agent with incomplete information for effective 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 coverage is 0%, so the description should compensate. It says 'by id,' which clarifies that case_id is an identifier, but adds no format or syntax details. Given only one required parameter, this is minimally adequate.

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 (Retrieve) and resource (a case by id), which is clear. However, it doesn't differentiate from siblings like get_case_outputs or unlock_case, so it falls short of a 5.

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 (retrieve a case by id), but there's no explicit guidance on when to use this vs alternatives like get_case_outputs or unlock_case. The description mentions 'once the case has been unlocked,' hinting at unlock_case, but doesn't state when to use this tool vs others.

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