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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description contributes only the implicit 'resolved market' prerequisite and says nothing about whether status is derived on-chain vs. indexed, whether it requires the caller be a claimant, or what the status values mean.

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?

One short sentence with no filler, so nothing is wasteful, but it is under-specified rather than concise and duplicates the title verbatim, so it does not earn extra informational value. There is no front-loaded routing or precondition detail.

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 and annotations are rich, so return values and safety need not be explained. However, for a tool sitting in a crowded cluster of claim and resolution siblings, the description omits the one thing an agent most needs: how to choose this call over the alternatives.

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 100% for both parameters, so marketAddress and chainId are already fully documented in the schema. The description adds no meaning beyond that, which is acceptable at the baseline for a fully covered schema but represents zero incremental value.

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?

Tautological: description restates name/title.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The implicit precondition is that the market must already be resolved, which an agent can infer, but nothing tells it whether to check status here versus via kellian_list_claims or kellian_get_resolution_status.

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