analyze_citation_gap

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

The description goes beyond the annotations by disclosing cost ('Costs 1 quota unit/call'), safety ('no side effects, safe to retry'), and error behavior ('or {"error"} if either side couldn't be fetched/parsed'). This adds meaningful operational context beyond readOnlyHint, idempotentHint, and destructiveHint.

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?

Every sentence earns its place: purpose, use case, safety/cost, return shape, alternatives, and arguments. The key distinction is front-loaded, and the return format is detailed but justified because there is no output schema.

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 lack of an output schema, the description fully specifies the return structure, the error case, cost, read-only behavior, and the correct alternative tool. An agent has everything needed to call this tool correctly and interpret its 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?

With schema description coverage at 0%, the description fully compensates by explaining each parameter: keyword is 'the topic/query to check' with an example, and your_url is 'full URL of your own page to compare' with an example. The schema only provides property names, so this semantic enrichment is essential and well done.

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 states a specific verb ('compare'), a specific resource ('your own page's structure against the AI-generated answer actually cited for this keyword'), and a concrete outcome ('concrete gaps to close'). It also explicitly distinguishes the tool from analyze_citation_structure, so an agent can select it without ambiguity.

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 gives explicit when-to-use guidance: 'Use this to answer what should I change on this page to get cited' and an explicit alternative: 'Use analyze_citation_structure instead if you just want the winning answer's shape'. This leaves no inference to the agent.

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