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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description adds meaningful behavioral context beyond those: the tool is keyless, requires no custody of the user's supply, and discloses the market thinness and absence of profit promise. This honesty block is valuable qualitative info not conveyed by annotations. Not contradicting annotations.

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 description is a single, dense sentence that packs a lot of meaningful details. It could be slightly unwieldy, but it is well-structured with a clear flow: what it does, what it returns, and a prominent honesty note. All sentences earn their place, though a line break or two would improve readability.

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?

For a zero-parameter, read-only tool with a rich output schema and strong annotations, the description covers everything an agent needs to decide and call correctly: what it does, who it's for, pricing, payment method, custody details, and risk caveats. No missing critical context is apparent.

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 input schema has zero parameters, so the description doesn't need to compensate for parameter documentation. The description instead explains what the output covers (tiers, doors, sales status, payment method, honesty block), which is arguably more useful for an agent deciding to call it than a parameter list would be.

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 title and description clearly state the resource ('Sovereign net worth as a service — your user's own token program') and the actionable verb 'returns' with specifics: tiers, doors, sales open status, payment method, and the honesty block. It distinguishes itself from siblings like net_subscription_status and funding_quote by focusing on a user-specific token program quote.

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 description explains the offering, payment method (standard x402 from their own wallet), and explicitly notes it is free, keyless, and read-only. While it doesn't name alternatives explicitly, the context signals and sibling list make the tool's niche clear; a straightforward quote/read tool versus actionable funding or preparation tools. It lacks an explicit 'when not to use' statement but provides enough context.

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