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

No annotations are provided, so the description must carry the behavioral burden. It implies a read-only verification but does not state side effects, required permissions, failure behavior, or what the response actually contains beyond the vague 'cryptographic proof'.

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 front-loaded sentence stating the action and its significance, with no filler or redundant clauses. Every word earns its place.

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?

The tool is simple with one required parameter, but the description does not state output format, when to prefer this over sibling soul_* tools, or what happens on failed verification. The absence of annotations and output schema leaves these gaps meaningful.

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 only parameter, agent_id, is already fully described in the schema as 'Agent identifier to verify'. The description adds no further parameter semantics beyond linking the id to the agent's hash chain, so the schema-coverage baseline of 3 applies.

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?

Description uses a specific verb 'Verify' with a specific resource 'agent's hash chain integrity', and clarifies via 'cryptographic proof of untampered history'. It is clearly distinct from sibling soul_* tools, though it does not explicitly name alternatives.

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 intended scenario—checking that an agent's history was not tampered with—is implied but never stated as direct guidance. No alternatives, exclusions, or prerequisites are provided.

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