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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds real value beyond that by disclosing the return vocabulary (native|sig|proof|weak tiers plus evidence), but says nothing about behavior on unknown DIDs, empty results, or pagination.

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?

One front-loaded sentence with no filler; the resource and scope come first and the return details follow. The parenthetical tier list is slightly cryptic out of context but earns its place by telling the agent what values to expect.

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-parameter read tool with rich annotations and no output schema, the description covers purpose and the essential shape of the response. Missing only edge-case behavior and DID format guidance, which are minor given the tool's simplicity.

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?

With a single parameter and 0% schema description coverage, the description must carry the meaning, and it does say the DID identifies the subject whose bindings are listed. It stops short of specifying the DID string format (e.g. did:method:id) or whether a partial/invalid DID is rejected, so compensation is partial.

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 ('List') and resource ('platform bindings for a DID') and even names the shape of the returned data (verification tier + evidence). An agent can tell this is a read of identity bindings, though it never explicitly distinguishes itself from siblings like wide_identity_resolve or wide_identity_bind.

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?

Usage is only implied: the description makes clear you call it when you want to enumerate a DID's bindings, but there is no explicit when-to-use/when-not or pointer to wide_identity_resolve as the alternative for fetching the DID document itself. The agent must infer the routing from the name alone.

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