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

It adds cost ($5.00), output nature (portable on-chain attestation), and verifiability without the service—context beyond annotations. Annotations already flag write/open-world/non-idempotent; the description does not explain payment mechanics or irreversibility, but there is no contradiction.

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 carries the price and key differentiator with little waste. 'Everything in one check' is slightly vague but still compact.

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 one-parameter tool with rich annotations, it covers cost and attestation output sufficiently. It leaves 'snapshot' and the check contents undefined, but not enough to block correct invocation.

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 single subject parameter is fully documented in the schema at 100% coverage, and the description adds no further parameter detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 name plus description identify a reputation attestation: 'everything in one check' plus a portable on-chain attestation of the snapshot. It differentiates from reputation_check by the added attestation, though it never explicitly says the check is reputation or what 'everything' includes.

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?

It signals use when a third-party-verifiable on-chain attestation is needed, and the $5.00 price helps compare against reputation_check. But it never names reputation_check or states when to use the cheaper check-only sibling, so guidance is implied rather than explicit.

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