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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds only mild context: the contradictions are 'recorded' (persisted state) and scoped to the 'authorized workspace'. Pagination behavior and result shape remain undisclosed.

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 front-loaded sentence with no filler; the scope constraint lands immediately.

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?

With 0% schema coverage, no output schema, and four undocumented parameters, the description is too thin for the agent to call this correctly. It never explains filtering (includeResolved) or paging, which are the only real decisions this tool exposes.

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% across four parameters, so the description carries the full burden and adds nothing: claimId, limit, offset and includeResolved are never mentioned. In particular, the default-false includeResolved filter and the limit/offset pagination bounds are left for the agent to infer from names.

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?

Specific verb ('Inspect') plus a clear resource ('recorded contradictions for a claim') and scope ('authorized workspace'). It does not distinguish itself from the sibling helvabase_resolve_contradiction, so an agent cannot tell read vs. act apart from the name alone.

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 statement of when to use this versus alternatives such as helvabase_resolve_contradiction, nor any prerequisite about how a claim gets contradictions recorded. Usage is only implied by the word 'Inspect'.

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