Competitor keywords

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context — and it adds almost none. With zero input parameters, the description never explains how the target competitor is identified (saved brand context? prior find_competitors call?), which is the most important behavioral unknown for this tool.

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?

One front-loaded sentence with no filler or redundancy. It is tight, though its brevity is partly a consequence of under-specification rather than deliberate economy.

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?

This is a low-complexity, annotation-covered, no-param tool, so a short description can suffice. The missing piece is how the competitor is selected given the total absence of inputs — that gap should be closed for an agent to invoke it with confidence.

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 tool takes no parameters, so there is no schema detail for the description to compensate for; baseline 4 applies. The description does not need to explain parameter syntax here.

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?

States a concrete verb ('See') and a specific resource ('Google keywords a competitor's website shows up for'), which clearly separates it from the sibling research_keywords (own keywords) by scope. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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 phrase 'a competitor's website' implies the tool is for competitor research rather than your own brand, which is useful implied context. However, it never says when to prefer this over research_keywords or how it relates to find_competitors/save_my_brand, and gives no prerequisites or exclusions.

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