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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: values stay hidden so later readers read blind. That is real context an agent cannot get from the schema. However, it never states that the operation is read-only, what happens if neither or both ids are supplied (required count is 0), or any error behavior, so the safety profile remains inferred.

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?

It is a single run-on sentence with deeply nested parentheses, an unbalanced closing paren, and a trailing fragment ('and which claims it opened'). The content is dense but not front-loaded, and the structural errors make it harder to parse than a short bulleted split between the claim mode and the proof mode would be.

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 two-optional-parameter read tool with no output schema, the description does a fair job describing the return payload in both modes. What is missing is the operational contract: whether one id is required, which takes precedence, and whether the call is read-only. Those gaps matter because nothing in the annotations covers them.

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%, so the description must compensate, and it partially does by tying claim_id to claim status and proof_id to proof status. It does not say the parameters are optional, mutually exclusive, or what the default behavior is when omitted, leaving the most decision-relevant semantics unstated.

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 names the resource and states what is returned: status of a claim (checks, decision, reason) or of a submitted proof (reading count, agreement, hidden values, claims opened). That is far more specific than a restatement of the name. It loses a point because it never distinguishes itself from plausible siblings like get, verify, or check_intake, and the sentence's dangling parenthesis ('and which claims it opened)') muddies which mode that clause belongs to.

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 guidance, no mention of when to prefer this over get/verify/query, and no statement of prerequisites or whether claim_id and proof_id are mutually exclusive. The only usage signal is implicit: the two modes follow from which id you supply, which the agent must infer.

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