Export Keywords Metrics

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

No annotations provided, so description carries full burden. It mentions 'POST form-data; source in query' but lacks behavioral details like rate limits, data freshness, error handling, or response structure. The schema caps keywords at 5000, but description does not reinforce or explain this.

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 concise (one sentence) and front-loaded with the core action. However, it includes technical details (endpoint, method) that could be moved to the schema or noted separately. It is adequate but not structured for maximum clarity.

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 complexity (5 parameters, no output schema, no annotations), the description is incomplete. It omits return value format, usage context among sibling tools, and any important behavioral notes. The schema provides param details, but the description adds little context.

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 baseline is 3. The description does not add extra meaning beyond schema; the parameters are already well-documented in the schema. The mention of 'source in query' is a minor technical detail.

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 'Bulk retrieve metrics for a list of keywords', specifying the action (retrieve metrics) and scope (list of keywords). The endpoint and method are provided, distinguishing it from sibling tools that focus on specific keyword queries like questions or related.

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 on when to use this tool vs. alternatives like keyword-specific tools. It does not mention when not to use it or provide any context for selection among similar tools.

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