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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description goes beyond them by disclosing that the call is free and by explaining what 'claimed' actually means (one signature covers every endpoint and host paid to that wallet), plus pagination with a total.

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 key qualifying detail ('Free.') and ending with the paging contract. The parenthetical on wallet/signature semantics is long but earns its place by defining the filter condition.

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?

An output schema exists, so return-value shape need not be explained, and annotations carry the safety profile. Combined with the qualification semantics, contents, and paging behavior given here, an agent has enough to call this 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 coverage is 100%, so both parameters are already fully documented with types, bounds, and defaults. The description restates the limit/offset paging model and the total but adds no syntax or format meaning beyond the schema, so baseline 3 applies.

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 identifies the specific resource returned (sellers who proved wallet control, with profile and endpoint counts) and clarifies the qualification semantics. It reads more as a description of the record set than an explicit action verb, and it does not differentiate itself from nearby siblings like settled_seller_reputation or settled_find_endpoints.

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 leading 'Free.' signals no cost barrier, implying this is a safe browse-first call, but there is no explicit when-to-use guidance or routing to alternatives such as settled_seller_reputation. Usage context is only implied.

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