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

Annotations already establish readOnly, idempotent and non-destructive behavior, so the description isn't burdened with the safety profile. It adds context the annotations lack: the call is 'Free,' it is paged with a total, and claims never alter scores. It stops short of describing sorting or what fields a profile contains, but with an output schema present that is acceptable.

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?

Information-dense with zero filler: cost, definition, when/when-not, and paging are all front-loaded and each sentence earns its place. 'Free.' as a leading word is a deliberate, useful signal.

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?

Given an output schema exists, return values need no explanation. Cost, use/avoid conditions, paging behavior and the relationship to scoring are all covered, so an agent has everything needed to select and call it correctly.

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%, so limit/offset are already fully documented with defaults and ranges. The description restates the limit cap and offset and adds that a total is returned, which is marginal value over the structured fields. Baseline 3 is appropriate.

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 defines the returned resource precisely: sellers who cryptographically proved control of the wallet their x402 endpoints are paid to, along with profile and endpoint counts. The verb is implicit rather than stated ('Paged: limit... offset'), but an agent can immediately tell this is a listing of verified/claimed sellers, distinct from the scoring-oriented siblings.

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 gives explicit when-to-use triggers (want a contact or docs link, or want to see which sellers stand behind their endpoints) and an explicit when-not with the alternative named ('Not for: judging an endpoint's quality... use settled_check'). Nothing is left to inference.

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