find_competitor_content_gaps

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context beyond annotations: it costs $0.10 USDC and explicitly disclaims live SERP verification. This informs the agent about cost implications and the tool's reliance on supplied data, which is useful for invocation decisions.

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, concise sentence that front-loads the core purpose, then adds two critical constraints (no live SERP verification, cost). No filler or redundancy; every element earns its place.

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?

The tool has moderate complexity (nested objects, two required params) but no output schema. The description covers input source and cost but does not mention what the output looks like (e.g., list of gaps, structured data). Since there is no output schema, the description should provide some expectation of return format, which it lacks. The provided context is adequate for invoking the tool but incomplete for fully anticipating results.

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 100% description coverage, with each parameter (site, competitors) and nested properties documented. The tool description adds minimal extra meaning beyond 'customer-supplied site and competitor pages', which is already clear from the schema. Baseline of 3 applies as schema handles the parameter semantics.

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: finding content gaps between a customer-supplied site and competitor pages. It uses a specific verb ('find') and resource ('content gaps'), and the scope (customer-supplied pages) distinguishes it from sibling tools like 'find_keyword_opportunities' or 'audit_site_seo'.

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 about when to use the tool: it requires customer-supplied site and competitor pages, and it explicitly notes it does not claim live SERP verification. This implies the tool is for analyzing provided data rather than live search results, but it does not explicitly name alternatives or mention when not to use it.

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