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

With no annotations, description carries full burden. It discloses the payment requirement ($0.01 USDC via x402) and explains that tools/call returns payment-required metadata, and invoice must be settled to fetch CSV. Provides moderate transparency about the data flow, though could detail more about rate limits or data freshness.

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?

Three sentences: first states purpose and format, second lists column coverage and use cases, third explains payment workflow. Front-loaded with key info, no wasted words.

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?

Explains return flow (metadata first, CSV after payment) and lists columns. No output schema, so description should cover structure; it references 'same column set as JSON variant' but doesn't detail schema. Lacks complete column list but is sufficient for credit.

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?

Input schema has zero parameters (100% coverage), so baseline is 4. Description adds nothing about parameters because none exist. This 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?

Clearly states it provides hardware-wallet buyer-intent and self-custody onboarding-friction intelligence as flat CSV. Lists specific use cases (Ledger vs Trezor, Bitcoin-only wallet research, etc.) and contrasts with the JSON sibling by specifying CSV format and optimized use for spreadsheet/pipeline ingestion and affiliate-routing or comparison-research workflows.

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?

Describes when to use (spreadsheet/pipeline ingestion, affiliate-routing/comparison-research workflows) and indirectly distinguishes from JSON variant. However, lacks explicit exclusions or when-not-to-use guidance.

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