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

readOnlyHint=true already signals a non-mutating read, and the description usefully adds that the evidence is frozen, running vote tallies are withheld, and private evidence has an access gate. These go beyond the annotation and help an agent anticipate authorization failures and missing data.

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 short sentences; the main action is front-loaded and the caveats are compressed. No filler or redundant restatement of the schema.

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?

The description gives the core scope and key limitations for a simple two-parameter read. However, with no output schema and no parameter guidance, an agent still lacks context for the 'round' parameter and what the returned rubric/evidence payload looks like.

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%, so the description carries the burden for explaining 'id' and 'round'. It defines neither: 'id' is only inferable as the case identifier from the tool name, and 'round' has no explanation of what it selects or defaults to.

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 opening 'Read frozen case evidence and rubric' states a specific verb and resource, so an agent immediately knows the action. It doesn't explicitly name sibling alternatives (e.g., list_adjudication_cases, open_evidence_case), but 'frozen' narrows the resource enough to distinguish it from ordinary case listing.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no sibling alternatives are named. 'Frozen' implies a status precondition, and the caveats about votes/private evidence are access constraints, not usage direction.

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