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

With no annotations, the description carries the behavioral disclosure burden. It discloses authentication/permission requirements, identifies the return content, and notes that the response may include a step only the person can do. The read-only nature is conveyed by the title and the word 'Returns', though error or not-found behavior is not discussed.

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?

The description is a single front-loaded sentence that covers the prerequisite and the return value without filler. The phrase 'any step only the person can do' is slightly awkward, but the overall structure is compact and scannable.

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 low-complexity, one-parameter read tool with no output schema, the description adequately covers authentication, selection, and return contents. It omits error behavior and case_id provenance, but these are minor gaps given how simple and focused the operation is.

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%, and the single parameter case_id has no dedicated description in the schema. The tool description connects case_id to case selection, but it does not explain the expected format or where to obtain the case_id, which would add value beyond the raw schema constraints.

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?

The description clearly states the tool reads and returns a single removal case by case_id, and it lists the specific fields returned (current status, verification status, and an actionable step). This differentiates it from the sibling list tools by focusing on one case, though it does not explicitly name those alternatives.

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 description implies the appropriate use case: when you have a case_id and need a single case's current status. It also provides a prerequisite by stating OAuth and the 'share_results' permission are required, but it gives no explicit contrast with sibling tools or guidance on when not to use it.

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