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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: results are public-safe, cryptographically signed, and omit claim text — important for an agent deciding whether the payload is sufficient. It stops short of disclosing what happens on an unknown case id (error vs. empty result) or what the returned history contains.

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 compact sentence with the most decision-relevant constraint ("no claim text") in parentheses at the end, so nothing is wasted. The tradeoff is that the terseness is achieved by dropping the verb and any usage context rather than by tight editing.

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 lookup with no output schema, the description covers the essential caveat about what the result does and does not contain, which is the main thing an agent needs. It is still incomplete on how to obtain a case id and what a signed history record looks like, both of which matter because there is no output schema to fall back on.

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?

There is one parameter, case_id, with 0% schema description coverage, so the description carries the full burden and adds essentially nothing: no format, prefix, or source for a valid case id. Since it does not compensate for the schema gap at all, it falls below the baseline.

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 title supplies a clear verb and resource ("Look up a dispute or notice by case id"), but the description body itself is a noun phrase, not a statement of action, and it never clarifies how this differs from close siblings such as outcome_dispute, dispute_record, or outcome_appeal. It does add a scoping fact (signed, public-safe, no claim text), which helps, but an agent must fall back on the title to know what the tool actually does.

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?

There is no when-to-use guidance: no statement of when this is the right lookup versus outcome_dispute or dispute_record, and no prerequisites such as where a valid case_id comes from. The only guidance-like element is the negative scope note "no claim text", which hints at a boundary but does not route the agent between alternatives.

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