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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses that publication is opt-in, only posture is exposed (a ceiling exists but never its value), and that found:false means not published rather than a negative signal. It stops short of describing rate limits or the exact response shape, but covers the key interpretive traps.

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?

The chain structure is front-loaded in the first sentence and each later sentence adds distinct behavioral meaning (count semantics, break meaning, opt-in posture, found:false). Dense but not padded.

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?

With no output schema, the description carries the burden of explaining return values and does so conceptually: per-link holds, a completeness count that is factual not a score, the break point, and found:false semantics. Exact field names or shape are not given, which is the only gap.

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?

There is a single parameter with 100% schema coverage, so the baseline is 3. The description adds nothing about agentId format or id semantics beyond what the schema already states.

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 concrete verb and resource: it resolves who stands behind a paying agent by walking the chain agent -> principal -> mandate -> credential -> wallet. That structural framing lets an agent tell it apart from the sibling verification/screening tools without opening the 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?

The scope ('a paying agent') implies when to reach for it, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage must be inferred from context rather than stated.

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