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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes further by disclosing what is actually verified (signature, Merkle proof, on-chain root in Stellar and a Bitcoin block) and the shape of the answer, plus that the call is free and needs no key. Return format beyond the verdict names is not detailed, but this is well above what the annotations carry.

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?

Content is dense and mostly front-loaded, but the opening rhetorical question and the parentheticals (any issuer / OpenTimestamps clauses) make it a single long run-on block. It earns most of its length, yet trimming the flourish would improve scanability without losing information.

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 complex external-verification tool with no output schema, the description covers purpose, the verification pipeline, the verdict vocabulary, and the anti-replay nonce flow. The one remaining gap is what the 'one sentence for your principal' and error cases look like, but an agent has enough to invoke it correctly.

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 75%, but the nested 'proof' object has no schema description (has nested objects = true), so the description carries that gap: it ties nonce+proof together as the holder-proof flow produced by prove_word_pass and explains url as the shown pass and agent_id as the PazAIr identifier. It adds genuine meaning over the bare schema, though field-level structure of the proof object is still unspecified.

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?

States a specific verb and resource (check a Word Pass), and enumerates exactly what is verified: signature, Merkle proof, Stellar root, and Bitcoin block via OpenTimestamps. It also names the verdicts returned (kept_its_word, no_badge_yet, invalid), so an agent can distinguish it from siblings like verify_pass, get_pass, and prove_word_pass without opening any schema.

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?

Gives an explicit triggering condition ("Before you trade with an agent you do not know, ask for its Word Pass and check it here") and a distinct escalation path: when the URL could have been copied, issue a fresh nonce and route through prove_word_pass with proof+nonce. Both when-to-use and the alternative are spelled out.

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