get_case

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 usefully discloses the return content of both branches (details include results, expert review, and performance), which goes beyond the schema. However, it says nothing about read-only semantics, authentication, or how many items constitute the 'recent case list' or how that list is ordered or paginated.

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 sentence that front-loads the decisive condition (case_id present vs absent) and enumerates the detail payload without waste. Nothing is padded.

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 one-parameter, no-output-schema tool, the description covers both operating modes and the content of the detailed result, which is what an agent needs to call it correctly. Minor gaps remain around list behavior (size, ordering) and the absence of any permission or safety note.

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 schema only labels the field 'Case Id' with a null default. The description adds real meaning by explaining that the mere presence or absence of case_id switches the tool between detail and list mode, which is not derivable from the schema alone.

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 names a specific resource (case) and clearly specifies two distinct behaviors: returning case detail (results, expert review, performance) when case_id is present, and listing recent cases when absent. It distinguishes itself from the obvious sibling save_case by being the read side, though it does not explicitly contrast with other read siblings like get_catalog.

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 by the conditional on case_id: pass an ID for detail, omit it for a list. That is useful routing guidance for the two modes, but there is no explicit statement of when to prefer this tool over alternatives such as get_catalog or compute_metrics, and no prerequisites or exclusions are given.

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