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

Annotations already declare readOnlyHint: true, and the description adds important behavioral context: the tool is free, AI-generated (implying non-deterministic results), and rate-limited. This informs the agent about potential limitations and cost implications, going beyond the annotation.

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, front-loaded sentence that efficiently communicates the tool's purpose and key constraints. No redundant words or filler; every phrase adds value, including the parenthetical note on being free, AI-generated, and rate-limited.

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 one-parameter tool with no output schema, the description covers the purpose, output features (keyword ideas with search intent and difficulty), and rate-limiting context. It stops short of detailing the exact return format or rate limit specifics, but is adequate for a simple generator.

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 description coverage is 0%, and the description only adds 'for a topic' without elaborating on what constitutes a valid topic (e.g., format, examples, length). While 'topic' is self-explanatory, the description does not fully compensate for the missing schema description, though the single param is simple.

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 generates SEO keyword ideas for a topic, and specifies the additional output features of search intent and difficulty. It distinguishes this tool from sibling generators by focusing specifically on keywords with SEO attributes.

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 implies usage when keyword ideas are needed for a given topic, but it does not provide explicit guidance on when to use this tool versus alternatives like content-idea-generator or keyword-density-checker. No exclusions or alternative tool references are mentioned.

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