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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context by disclosing cost ($0.01 or included in a plan key), which an agent needs before calling. It stops short of describing rate limits or response shape.

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 return-field list is front-loaded and the pricing note is tucked into a trailing parenthetical. Two sentences and a parenthetical, each doing work, though the stock_issuer aside is somewhat tangential given it is not a sibling tool.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields and the 0-100 score. Combined with annotations covering the safety profile and the disclosed cost, an agent has enough to call it correctly; only edge details like chain scope or error behavior are absent.

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 100% schema description coverage ('Deployer wallet 0x…'), the schema already carries the semantics. The description adds no format, chain, or validation detail beyond what the schema states, 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 names a specific resource ('Deployer reputation record') and enumerates exactly what it contains: tokens launched, real vs dead, best-token volume, insider-distribution flag, and a 0-100 score. It further disambiguates by contrasting with stock_issuer, so an agent can tell it apart from token/wallet/issuer 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?

Usage is only implied: it is clearly a per-deployer lookup keyed by wallet address, and the stock_issuer note gives one routing distinction. However, stock_issuer is not in the sibling list, and there is no explicit statement of when to prefer this over robinx_token, robinx_wallet, or robinx_arc_deployer.

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