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

No annotations are provided, and the description does not disclose any behavioral traits such as output format, rate limits, or side effects. It only mentions billing per call, which is a cost detail, not a behavioral disclosure. This is a significant gap for a tool that makes external calls.

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 minimal (one sentence plus metadata) and could be considered concise, but it is under-specified rather than appropriately sized. The Group and Billing information is extra but not harmful. However, the brevity undermines usefulness.

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 the lack of output schema, parameter descriptions, and usage guidance, the description is far from complete. The tool performs a specific type of keyword research, but the description fails to convey essential context like the data source (Google), return structure, or limitations.

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 2 parameters with no descriptions and 0% schema coverage. The description does not mention 'country' or 'keyword', nor does it explain their format, defaults, or optionality. The agent has no guidance on how to fill these fields effectively.

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 'Find thousands of relevant keyword ideas' which is a clear verb+resource, but it does not explicitly mention Google or differentiate from sibling tools like Amazon, Bing, or YouTube keyword generators. The Group and Billing notes add operational context but not purpose specificity.

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 guidance on when to use this tool versus the other keyword generator variants. No context, prerequisites, or exclusions are provided, so an agent would not know if this is the right tool for a Google-specific search.

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