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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that the tool is "free" and shows "current" status, which provides some context beyond annotations, but it doesn't disclose response format, pagination, or potential limitations. The added value is modest.

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 sentences, with the first sentence front-loading the verb and resource, followed by a concise list of included data. The second sentence is minimal and directly useful. No filler or redundant 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?

With an output schema present and zero input parameters, the description covers the essential context: what the tool lists and that it's free. The tool's simplicity means the description is complete enough for an agent to select and invoke it correctly.

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 has zero parameters, so the baseline is 4. The description doesn't need to explain parameters since there are none, and it doesn't add any parameter-level detail because there's nothing to add.

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 uses a specific verb "List" and clearly identifies the resource as "EXVIV competitive-intelligence products," further detailing the included data (x402 commerce status, inputs, markets, prices, evidence coverage). This distinguishes it from sibling tools like compare_competitor_offers or get_company_pricing, which focus on comparisons, pricing, and evidence briefs respectively.

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?

No explicit when-to-use or alternatives are mentioned. The phrase "List EXVIV competitive-intelligence products" implies an overview/catalog use case, but the description does not state when to prefer this over sibling tools or mention any exclusions. It's a clear but only implied usage context.

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