Compare your page with competitor pages

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds value by enumerating exactly what data is extracted (word count, heading counts, content terms, etc.) and the content-gap hint, giving the agent a clear picture of the operation's scope without contradicting 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 compact, two sentences, with the core purpose front-loaded and details listed in a structured manner. No redundant filler, though the list of metrics is extensive, it is still efficient.

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 no output schema, the description lists the data points it returns but does not explain the output format or structure. It also omits clarification of the gapTerms parameter and does not mention that pages are fetched live, though openWorldHint implies external access. Given the complexity, the description is adequate but not fully complete.

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 0%, so the description must compensate. It implicitly maps 'yourUrl' and 'competitorUrls' via the text, but the 'gapTerms' parameter is entirely undocumented in both the schema and the description. The agent cannot infer its purpose or constraints from the description alone.

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: auditing multiple URLs side by side, listing specific metrics (word count, headings, links, schema types, etc.) and explicitly mentions comparing 'yours plus pages ranking above you'. This differentiates it from single-page audit tools like page_audit and structured_data_audit.

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 for competitive analysis but does not explicitly state when to use this over alternatives, nor does it mention any exclusions or conditions. It provides context (comparing with competitor pages) but lacks explicit routing guidance.

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