get_keywords_bulk

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

With no annotations, the description carries full transparency duty. It only states 'get keywords in bulk' without explaining what data is returned (e.g., volume, competition), how filtering works, or any behavior like pagination. Minimal disclosure.

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 (one sentence), but it is too sparse to be considered appropriately sized. It is not front-loaded with critical information and reads more as a placeholder than a well-structured summary.

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 22 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the tool's core functionality, the meaning of filters, or the expected output, making it nearly useless for an 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?

Schema coverage is only 14% (3 of 22 parameters have descriptions). The description does not add any parameter-level meaning beyond the schema. It fails to explain the purpose of key parameters like volume_min, competition, or include/exclude, leaving the agent with insufficient context.

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 'Obtenir des mots-clés en masse' (Get keywords in bulk) clearly identifies the verb and resource, but it lacks specificity about what 'bulk' means compared to siblings like get_keywords_find or get_keywords_match. It does not indicate whether it accepts multiple keywords as input or returns aggregated data, making it only adequate.

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 provides no guidance on when to use this tool versus the many sibling keyword tools. No context about prerequisites, when it is appropriate, or when to avoid it. This is a significant gap.

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