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

Annotations already establish read-only, open-world, non-destructive behavior, and the description adds relevant traits: no pagination, missing values are not zero, source-freshness rules, and owner-only results remaining in call history. Some caveats such as "Prices and publication are unapproved" are opaque, but they do add behavioral context beyond the annotations without contradicting them.

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 short and front-loads the purpose phrase, but it is a stack of terse caveats rather than a structured explanation. Sentences such as "Prices and publication are unapproved" and "Successful owner-only results remain available in call history" are not clearly relevant to a domain-competitor lookup.

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 four parameters, one required target, and no output schema, the description is incomplete. It mentions missing evidence and freshness but does not explain what a result contains, what `target` represents, or how market and language affect the answer.

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 description coverage is 0%, and the description does not explain any of the four parameters. It never clarifies what `target` should be (domain, URL, keyword set), what `market` and `language` constrain, or how `limit` relates to the stated no-pagination behavior.

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 first sentence, "Shared Organic Keyword Competitors," essentially restates the title and does not add a verb, scope, or clear statement of what the tool returns. It is possible to infer a domain-competitor keyword tool from the name, but the description itself remains tautological and does not distinguish it from sibling SEO competitor or keyword-intersection 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 gives no guidance on when to use this tool versus alternatives such as domain_keyword_intersection, serp_competitors, or backlink_competitors. "One fixed task; no pagination" is a constraint, not a usage rule, and there are no exclusions or prerequisites.

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