buy-from-underground

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

With no annotations, the description fully discloses the core behaviors: free vs. paid item handling and the payment requirement (USDC on Base/Solana). However, it could mention error handling or response format for invalid product IDs.

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, second details behavior, third provides usage guidance. No redundant information; every sentence adds value.

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?

Given one parameter and no output schema, the description covers input, behavior differences, and prerequisite. It could be more complete by describing the expected response format or error scenarios, but is adequate for the tool's simplicity.

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% with a description that supports partial match. The tool description does not add beyond the schema; it only reiterates the prerequisite. Baseline 3 applies as the schema already describes the parameter adequately.

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 clearly states the tool retrieves purchase or delivery links for products, distinguishing between free (direct URL) and paid (x402 endpoint requiring USDC payment). This verb+resource+scope is specific and differentiates from siblings like search-underground or get-free-content.

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 explicitly states to 'use search-underground first to find product IDs,' providing clear prerequisite context. It implies when to use this tool but does not explicitly list exclusions or alternatives, though the sibling tools suggest other uses.

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