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

Annotations already flag this as a non-read-only, non-idempotent, open-world operation, so the description's job is to explain consequences. It does add real context: a one-time seal is issued (consistent with idempotentHint=false), execution aborts for unknown or revoked agents, and there is a per-call x402 charge of $0.06 USDC, which is a fact nowhere in the structured fields. It loses a point for not explaining what "publish the badge" makes visible, whether the seal is consumed on failure, or where the target agent identity comes from.

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 short sentences: the operation sequence first, then the blocking condition, then pricing in parentheses. Nothing is padded and the ordering is sensible. The opening phrase "Verify who you are stamping for" is slightly cryptic and could have been one word more explicit about the target agent.

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 multi-step composite that mints and publishes artifacts, the caller still lacks key facts: what is returned (seal identifier, badge URL, receipt) since there is no output schema, how the target agent is specified given only a `task` parameter, and whether publishing is public or scoped. The cost and abort conditions are covered, so it is not inadequate, but it is not complete for the tool's complexity.

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 coverage is 100% for the single `task` parameter, so baseline is 3. The description adds no meaning about what the task text should contain, and it introduces an unresolved question: it claims to verify "the agent" but exposes no parameter identifying that agent, leaving the caller to guess that identity is implicit from auth or earlier context.

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 a concrete three-step sequence with specific verbs and resources: verify the target, issue a one-time seal, publish a trust badge. That is far more informative than the name alone. It stops short of 5 because the sibling set contains the constituent pieces (attestation.single-use-seal, agent.trust-badge) and the description never says how this bundle relates to or differs from calling them individually.

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?

"Verify who you are stamping for, issue a one-time seal, then publish the trust badge" implies the scenario (you have a target agent and want a seal plus badge), but there is no explicit when-to-use or when-not-to-use against attestation.single-use-seal or agent.trust-badge. The precondition "Stops if the agent is unknown or has revocations" is the closest thing to selection guidance, and it describes blocking conditions rather than routing rules.

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