Similar Keywords

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

The description only states the core action and endpoint. It does not disclose behavioral traits such as pagination behavior, rate limits, response structure, or any side effects. Since no annotations are provided, the description carries the full burden and fails to address these.

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 very brief (one sentence) and could be more informative without becoming verbose. It sacrifices valuable context for brevity, but it is not overly long.

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 20 parameters and no output schema, the description is insufficiently complete. It should explain what 'similar' means, how pagination works, and what the response contains. The current description leaves significant gaps for the agent.

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 input schema has 100% description coverage for all 20 parameters, so the schema already explains each parameter. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 it fetches similar keywords from a specific API endpoint. However, it does not differentiate 'similar' from sibling tools like 'keywordsRelated' or 'keywordsLongtail', which could cause confusion about when to use this tool.

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?

No guidance is provided on when to use this tool versus its siblings. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer when 'similar' is appropriate.

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