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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the evaluation criteria but does not clarify what the tool actually returns (e.g., a boolean, a structured assessment) or any side effects (it appears inert, but is not stated). Given no annotations, this is a moderate gap; the description is not misleading but incomplete.

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, concise sentence that immediately front-loads the core purpose and criteria. Every word contributes to understanding. It is appropriately sized for a simple tool.

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?

Given the tool's moderate complexity (checking three conditions), the description covers the 'what' but not the 'how' or 'return value'. Since there is an output schema (though not detailed in the context), the description does not need to explain return values, but it still lacks context on expected input format and examples. However, for a simple check, it is adequate but not rich.

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%, meaning the schema provides no description for the 'claim' parameter. The description adds some meaning—it implies the claim is a binary claim about a deadline, settlement source, and condition—but it does not define what constitutes a 'binary claim' or provide format examples. With only one parameter and minimal description, the compensation is insufficient.

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 states a specific verb ('Check') and a specific resource ('a binary claim') and names the three conditions it evaluates ('names a deadline, a public settlement source, and a clear condition'). It conveys the purpose clearly, though it does not explicitly distinguish from the sibling 'brier_summary'.

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 guidance on when to use this tool versus 'brier_summary'. The description implies it is for checking decidability, but it does not state contexts where brier_summary would be preferred or when not to use this tool. No exclusions or alternatives are mentioned.

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