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

The description adds context the annotations do not: no authentication is required, results are ordered with badge holders first, and the data comes from the last daily root anchored in Bitcoin and Stellar (freshness/provenance). However, the annotations declare readOnlyHint=false and idempotentHint=false for what reads like a pure listing, and the description does nothing to explain that side-effect posture or the return shape.

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?

A single dense sentence that front-loads what the register is before the qualifying details. It earns most of its words, though the 'root anchored in Bitcoin and Stellar' clause is jargon-heavy and could be split for scannability.

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-optional-param, no-output-schema tool, the description covers who appears, ordering, provenance and access cost. It still leaves the agent guessing what a register entry actually contains and how the anchoring affects trust decisions.

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 100% and the single optional 'limit' parameter is documented in the schema with an example, so the baseline applies. The description adds nothing about paging, defaults, or maximums beyond what the schema already says.

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 identifies the resource precisely (the public Word Pass register) and its scope (agents with records from paid, delivered orders), which separates it from point-lookup siblings like check_word_pass, get_pass or verify_pass. The verb is only implicit (a 'register' means a listing), so it stops short of an explicit 'list all X' statement.

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 says access is 'Free, no key', which is a useful prerequisite, but it never states when to call this instead of check_word_pass, verify_pass, get_pass, prove_word_pass or word_pass_signals. With eight sibling tools in the same namespace, the absence of routing guidance is a real gap.

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