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

Annotations already declare the non-read-only, non-idempotent, open-world mutation profile, and the description adds real behavior on top: the nonce is single-use, `challenge` yields "what to sign or publish", and OAuth kinds return an `auth_url` for a browser handoff. It omits failure modes, whether a failed link can be retried with the same nonce, and any rate/permission constraints.

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?

Front-loaded with the purpose, but the remainder is a single dense run-on sentence with nested parentheticals that are hard to parse on a first read. Little is wasted, but the lack of any structure or action-level separation costs clarity.

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 an 8-parameter, four-mode tool with an output schema and full annotation coverage, the description covers all four action branches, the sequencing between them, and the identity prerequisite. The one obscure phrase ("domain and ens: kind and value after their setup") is minor against otherwise complete dispatch documentation.

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 already 100%, so per-field meaning is covered; the description's added value is cross-parameter: it maps which parameters belong to which action (kind+value+proof+nonce for link, nonce+solution for work, bits for pow) and notes the domain/ENS special case. That action-to-parameter dispatch is meaningfully beyond the flat schema.

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+resource ("Raise your standing") and then enumerates the four action modes it supports, so an agent knows this is a multi-step credential/standing workflow rather than a simple lookup. It does not, however, distinguish itself from the sibling `standing_ways`, which plausibly overlaps with `action ways`, and never defines what "standing" means in this domain.

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 a clear procedural path: `ways` to discover kinds, `challenge` to obtain a nonce, then `link` or `work` to complete. It also states a prerequisite ("Needs a hosted identity (create_identity)") and routes OAuth kinds to the human's browser. It stops short of saying when *not* to use this tool or why to prefer it over `standing_ways`/`verify_publish`/`log_proof`.

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