Get Competitor Top 100

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

No annotations exist, so the description must cover behavior. It only states the basic function without disclosing traits like read-only nature, pagination, error conditions, or performance. The description is insufficient for a no-annotation 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?

The description is a single sentence but includes a redundant note about requiring a project ID (already in schema). It is front-loaded with 'Project Tool' but could be more concise. No severe bloat, but room for improvement.

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?

Given no output schema, the description should explain return format or pagination. It does not. The tool retrieves results for multiple keywords but the description is vague about structure. Incomplete for agent to infer full behavior.

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 baseline is 3. However, the description introduces ambiguity by suggesting a fixed 'top 100' while the 'top' parameter allows configuration (0..100). It adds no extra meaning beyond the schema and slightly misleads about the default 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 description clearly states the tool retrieves top 100 results for tracked keywords in a project, with a specific verb 'Get' and resource 'list of top 100 results'. It distinguishes from sibling PROJECT_getCompetitorTop10 by specifying the count (100 vs 10).

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 only mentions a prerequisite (requires project ID) but provides no guidance on when to use this tool versus alternatives like PROJECT_getCompetitorTop10 or other SERP tools. No exclusions or context for selection.

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