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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety of the operation is covered. The description adds genuinely non-obvious behavioral context: the response aggregates badges, their source Moments, and collections with pending signatures, and it warns that names/descriptions from other issuers are untrusted third-party content to be treated as data. It stays silent on pagination and return shape, which is the remaining gap.

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 sentences, front-loaded with the payload and followed by the injection warning, with no filler. The middle clause ('the collections they issue with what's waiting to be signed') is slightly tangled and takes a second read to parse.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so at a conceptual level: badges, source Moments, issuing collections, pending signatures. It could be more explicit about the response structure or whether results are paginated, but for a zero-arg read tool it is close to sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and baseline 4 applies. No scope or filter arguments exist that would need explanation.

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 names a specific resource (soulbound badges held in the link owner's linked wallets) and adds the composite scope: the originating Moment for each badge and the issuing collections with pending signatures. It does not differentiate itself from close siblings such as my_soulbound_collections or list_pending_soulbound, which appear to overlap with the second half of what this tool returns.

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 by the possessive framing ('I hold') – an agent can infer this is a personal read of its own badges. There is no explicit when-to-use, no exclusion, and no pointer to alternatives, even though list_pending_soulbound and my_soulbound_collections plausibly cover subsets of this output.

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