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

The description discloses key behaviors beyond annotations: domains are normalized to hostname, duplicates are dropped, the list replaces the current one, and an empty list clears it. It also mentions reconciliation with AI Visibility. Annotations already indicate idempotentHint=true and destructiveHint=false, and the description adds meaningful context about the replacement semantics and normalization.

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 and front-loaded with the core action ('Replaces the website's competitor list'), followed by key behaviors and usage guidance. Every sentence adds value, and the structure is easy to scan.

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 description covers the tool's purpose, replacement semantics, normalization, clearing behavior, AI Visibility reconciliation, return value, and website_id conditionality. With a rich schema and output schema present, nothing critical is missing for an agent to 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?

Schema coverage is 100%, so the schema already documents both parameters. The description adds value by explaining the replacement semantics ('Pass the complete list you want to keep'), the empty-list clearing behavior, and the website_id conditionality. It doesn't add syntax details beyond the schema, but the behavioral context compensates.

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 replaces the website's competitor list with a complete list of up to 10 name+domain entries. It distinguishes itself from siblings by focusing on the competitor list update, which is unique among the listed tools.

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 explicitly explains when to use this tool: pass the complete list to keep, empty list clears it, and it mentions the reconciliation behavior when AI Visibility is active. It also provides guidance on when website_id is needed, referencing get_account for multi-website accounts.

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