Organic competitors

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

No annotations are provided, so the description must carry the full burden. It reveals that results include shared keywords and traffic, but omits details about response structure, pagination, rate limits, or whether any filters are applied. This is a significant gap for a tool without annotation support.

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 single-sentence description is concise and front-loaded, with no unnecessary words.

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?

With no output schema and no annotations, the description should provide more context about the response format and data interpretation. It mentions 'shared keywords and traffic' but leaves the output structure ambiguous. The tool is simple but the description is incomplete for an agent to understand what to expect.

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 schema already documents 'target' and 'country' with descriptions; 'limit' lacks a description. The tool description adds no parameter-specific information, failing to compensate for the missing 'limit' explanation. With 67% schema coverage, the description should add value but does not.

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 defines the tool's function: identifying competitor domains in organic search, including shared keywords and traffic. This distinguishes it from sibling tools like 'organic-keywords', which focus on keywords rather than domains.

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 the use case (finding competitors) but provides no explicit guidance on when to use this tool versus alternatives like 'related-keywords' or 'organic-keywords'. No exclusions or prerequisites are mentioned.

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