Export Keywords Metrics

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It only states 'Retrieves metrics' but does not clarify if it is read-only, whether it modifies data, or any other side effects. There is no mention of rate limits, cost, or idempotency.

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 sentence which is concise but omits potentially useful context. It could be more structured, e.g., with a brief note on what metrics are included or how to use the parameters.

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 tool with 5 parameters and no output schema, the description lacks completeness. It does not describe the return format, pagination, or error conditions. The schema covers parameter details, but the description fails to synthesize a complete picture 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?

Schema coverage is 100%, so the description adds minimal value beyond the schema. While the description labels it as 'metrics for a bulk list of keywords,' it does not elaborate on parameter meanings or provide examples. Baseline 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 retrieves metrics for a bulk list of keywords. The title 'Export Keywords Metrics' aligns well. However, it could better differentiate from sibling tools like DATA_getDomainKeywords which retrieves keywords for a domain rather than metrics on a provided list.

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 such as DATA_getDomainKeywords or DATA_getRelatedKeywords. The description does not mention prerequisites or contexts where this tool is appropriate.

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