Purchase a market brief

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

The description discloses the cost and read-only nature, but the term 'purchases' suggests a write transaction, potentially contradicting 'read-only'. It does not explain authentication requirements or return behavior. Without annotations, more clarity on side effects would improve transparency.

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 sentence of 11 words, conveying essential information (cost, platform, type) without superfluous content. It is well-structured and front-loaded.

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 explains the action and cost but lacks details on what is returned (the brief content), authentication needs, and post-purchase behavior. More context would improve completeness.

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 provides 100% coverage for the single 'slug' parameter, including pattern and description. The tool description adds no additional meaning beyond the schema, so baseline score 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?

The description clearly states it purchases a market brief, specifies the cost (0.05 USDC), indicates it is read-only and structured, and names the platform (Base). This distinguishes it from sibling tools like get_market_delta, get_market_pricing, and list_trending_markets.

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 implies use when a structured intelligence brief is needed for a specific slug, but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites beyond the slug parameter.

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