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

Annotations already declare read-only and non-destructive behavior, so the description carries a lower burden for safety. It adds important behavioral context: the synthesis is built from live web sources, includes a signed provenance receipt, and costs $1.00 USDC per call. It does not disclose return format, latency, or rate limits, but for a read-only call the added details are meaningful.

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 two short sentences, front-loaded with purpose and followed by the critical cost detail. There is no filler or repetitive boilerplate beyond the minor 'synthesis/synthesized' repetition, and each sentence adds essential information.

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 one-parameter, read-only tool, the description is largely complete: it identifies what the tool returns (a synthesis plus provenance receipt), the data source, and the cost. It lacks an explicit output schema or return format, but the core details needed to invoke and understand the tool are present.

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 sole parameter 'market' has no schema description, and the description only clarifies it should be a 'market category'. This is minimal compensation for 0% schema coverage—no examples, format, or allowed values are given—but the single parameter is reasonably self-explanatory.

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 synthesizes a competitive landscape for a market category and enumerates its core outputs: current leaders, positioning, and dynamics. It also adds distinguishing elements—live web sources and a signed provenance receipt—that separate it from generic sibling signals or benchmarks.

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?

Usage context is implied: it is for obtaining a synthesized competitive landscape for a market category. However, it provides no explicit when-to-use/when-not-to-use guidance and does not mention alternatives like get_category_ai_leaders or get_competitive_displacement_signal, leaving the agent to infer tool selection.

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