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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that it returns a 'structured, audited deliverable' and mentions server-side validation. It does not detail other behaviors like data freshness, rate limits, or what 'open world' implies. No contradiction with annotations.

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 moderately sized but includes some redundancy (e.g., the title appears in both annotations and description). The key purpose is front-loaded, and the reference case is helpful. However, it could be more concise and better 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?

Given the complexity (nested objects, 4 parameters, no output schema), the description is incomplete. It does not explain the return format, typical response time, or how the 'focus' parameter affects results. The structured deliverables are not detailed, leaving agents without enough context for reliable invocation.

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 description coverage is low (25%). The description mentions 'selfCompany' and 'competitors' but does not elaborate on 'focus' or 'async' parameters. It adds minimal meaning beyond the schema, failing to compensate for the low coverage. The phrase 'send the documented case fields' is vague.

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 identifies the tool's purpose: comparing competitor pricing plans and monthly prices. It uses a specific verb ('Radar') and refers to a concrete reference case (Notion vs ClickUp, Asana, Coda). While 'Radar pricing concurrents' is somewhat hybrid, the overall intent is clear and distinguishes it from sibling tools like competitor_pricing_scrape.

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 usage when a structured deliverable comparing competitor pricing is needed, and it mentions that inputs are validated server-side. However, it does not explicitly state when to use this tool over alternatives (e.g., competitor_profiles or competitor_pricing_scrape) or provide exclusion criteria.

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