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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It importantly reveals the payment model ('Preview is free — $5 USDC via x402 unlocks the full analysis') and implies the tool returns a preview that requires payment for full results. It also lists the kind of data returned. While it doesn't discuss rate limits or auth beyond the payment, it does add significant behavioral context beyond a bare 'analyze a service'.

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 only two sentences, front-loading the core purpose and outputs in the first sentence, then the input format and payment in the second. Every sentence carries necessary information, with no filler or redundancy. It is both concise and well-structured.

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 tool with a single parameter, no output schema, and no annotations, the description is remarkably complete. It explains the purpose, the nature of the analysis, the specific outputs, the input format, and the critical payment behavior (preview vs. full access). The only minor omission is explicit mention of the return format (e.g., JSON), but the listed output data points sufficiently convey what the user will receive.

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%: the single parameter 'query' is fully described as 'Service ID, domain name (e.g., 'heurist.ai'), or URL to analyze'. The description repeats this same input guidance without adding new details such as examples, constraints, or ambiguity resolution. Therefore it meets the baseline for high schema coverage but adds no extra value.

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's function: 'Deep competitive analysis of any service' with a specific list of outputs (composite score, competitive percentile, revenue data, top competitors, strategic recommendations). This distinguishes it from sibling tools like market_overview or find_opportunities by focusing on single-service deep analysis with concrete deliverables.

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 provides clear context for when to use the tool: when a deep competitive analysis of a specific service is needed. It specifies input format ('Pass a domain name, URL, or service ID'). However, it does not explicitly mention when not to use it or direct users to alternatives like market_overview or market_pulse for different needs, so it falls short of a 5.

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