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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, and the description adds real context on top: verification happens against the platform's public API (explaining the open-world surface), and a handle already bound to another DID is rejected. It stops short of describing what a successful response contains or whether repeating the call with the same proof is safe given idempotentHint=false.

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?

Two dense sentences, front-loaded with the action and the precondition, then the proof format, then the verification behavior. No filler, though the parenthetical example list '(gist, post, comment, note id)' is slightly loose.

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 mutating, open-world, non-idempotent registration with four undocumented required parameters and no output schema, the description covers the mechanism and one failure mode but omits supported platform values, handle formatting, and what the call returns or how failures other than duplicate-binding manifest.

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 0% across 4 required parameters, so the description must compensate. It does so thoroughly for 'proof' (URL form, hex for EVM, JSON {pubkey,sig} for Solana/NEAR), which is the hardest parameter, but leaves 'platform' with no allowed values and 'handle' with no format convention (e.g. @-prefix), so half the surface is still implicit.

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 states a specific verb+resource: 'Register a DID↔platform-handle binding', and frames it as a publish-then-bind step. It is clearly distinguishable from wide_identity_list/resolve/revoke by the binding-registration action, though it never names a sibling explicitly.

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?

'after publishing/signing the bind statement' gives sequencing guidance implying a challenge/sign step must precede this call, which is useful. However, it never states when to use this versus wide_identity_revoke or wide_identity_resolve, nor what to do if the preconditions are not met.

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