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

The description adds genuinely useful behavior (allocation basis, escrow emission, exactly-once semantics), but it conflicts with structured data: 'Exactly-once — re-ruling returns the existing ruling' asserts idempotent behavior while idempotentHint=false says repeated calls have additional effect. Likewise, emitting a release/refund escrow instruction is an irreversible financial action, which sits awkwardly against destructiveHint=false; the agent gets contradictory signals about retry and reversal safety.

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, front-loaded with the action, then the mechanism and the exactly-once guarantee. No filler, no restatement of the title.

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?

An output schema exists, so return values need not be described, and the core mechanics are covered. What is missing for a state-changing, financially consequential tool is preconditions, error behavior (e.g., insufficient evidence), permission requirements, and any warning about irreversibility, which the annotations actively understate.

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 only one parameter, case_id, with 0% schema description coverage, and the description does not mention it at all. Its meaning is largely self-evident from the sibling tools, so this is a modest gap rather than a blocking one, but the description does nothing to compensate for the missing schema text.

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 uses a specific verb and resource ('Issue the deterministic ruling') and explains the mechanism: allocation of 100% of the disputed amount from evidence weights and trust scores, plus an escrow instruction (release/refund). That effect chain distinguishes it in practice from siblings like verify_ruling and set_trust_scores, though it never names those alternatives explicitly.

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?

It states what the ruling does but not when it should be invoked: no prerequisites (must evidence be submitted, must trust scores be set first?), no indication of how it relates to verify_ruling, and no guidance on what to do if the case is not ready. The agent must infer the workflow position from the sibling list.

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