us_get_case

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

Annotations already provide readOnly, idempotent, and non-destructive hints. The description adds that the tool uses a keyless search endpoint and avoids the authenticated endpoint, which is useful context but not critical behavioral disclosure beyond what annotations convey.

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 sentences with no unnecessary words. Each sentence conveys essential information: purpose and implementation detail. Efficiently structured.

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 simple retrieval tool with annotations and an output schema, the description is mostly complete. It could mention response format or error conditions, but the existence of output schema mitigates this. The guidance on parameter sourcing adds value.

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?

The input schema fully documents the parameter with example and source. The description reaffirms that cluster_id is the identifier, but does not add new semantic details beyond the schema.

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 fetches one opinion cluster by its CourtListener cluster_id, using a specific verb and resource, and distinguishes it from siblings like us_search_case_law by specifying it is a fetch operation based on an ID.

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 indicates the parameter source (from us_search_case_law) and notes the deliberate choice of keyless endpoint over authenticated, but does not explicitly state when to use or not use this tool versus alternatives beyond the endpoint choice.

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