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

With read-only/idempotent annotations already provided, the description adds useful behavioral context: the time-varying access state, the restarted fuse_expires_at, and the fact that an operator token is also accepted on the route. It does not contradict the annotations and enriches them without overloading.

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?

Three front-loaded sentences carry the core operation, the payload highlights, and the auth nuance without repetition. Each clause earns its place, though the operator-token sentence is slightly dense.

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 read-only, two-parameter tool with no output schema, the description covers the endpoint, auth, claim_id origin, and the key fields returned. It doesn't describe the full response structure or error cases, but what an agent needs to select and invoke the call correctly is present.

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?

The input schema already covers both parameters with descriptions at 100% coverage, so the baseline is 3. The description does not add new parameter-level semantics beyond noting the agent token and the operator-token route alternative, which is useful but not essential.

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 opens with a clear verb-resource pair ('Read one of your claims') and anchors it to an explicit GET route, so an agent can identify the operation. It distinguishes the data as claim-specific and as carrying what the public ledger withholds, but it doesn't name or contrast sibling tools like get_bounty.

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?

The context is clear: use this when the caller needs the non-public details of a claim (brief, access state, rejection reason) rather than public ledger data. It stops short of explicitly naming alternatives or stating when not to use it, so it misses the top tier.

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