Competitor semantics

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

The description adds one useful behavioral detail: the operation may consume SEO Intellect account limits, and it names the upstream API. However, it does not disclose async/task behavior, quota specifics, or what side effects occur beyond the annotation's readOnlyHint=false.

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 concise and front-loaded with the core purpose. The account-limits warning is valuable, though 'Upstream API tool: semantic' adds only marginal information beyond the tool name itself.

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 an async task/poll pattern and no output schema, the description is too sparse: it never mentions that a task_id can be submitted, that results may arrive asynchronously, or what a successful response looks like. The schema carries most of the burden, leaving the agent without enough standalone context.

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 the key parameters such as timeout_ms, wait_for_result, poll_interval_ms, and task_id, with 100% schema description coverage reported. The description adds no parameter-level meaning, so the baseline score applies; the two invocation modes are only discoverable from the schema.

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 operation ('Analyze a domain's visible keyword semantics') with a clear resource, and the title 'Competitor semantics' reinforces intent. It does not explicitly distinguish this from sibling tools like lsi or wordstat, so it falls just short of a perfect score.

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?

There is no explicit guidance on when to use this tool versus alternatives, and no sibling tools are named. The phrase 'domain's visible keyword semantics' implies a use case, but it does not clarify when to choose this over similar analysis tools.

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