keyword_analyze

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

No annotations are present, so the description carries the full burden. It mentions what the analysis returns but does not disclose side effects, auth requirements, rate limits, or whether it operates on cached data. This is insufficient for a tool with no structured safety metadata.

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 two sentences, each earning its place: the first explains functionality, the second gives the trigger scenario.

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 tool's simplicity (one parameter, no output schema), the description covers purpose and use case. However, it omits details about the output structure, any dependencies on cached data, and whether it's a synchronous call, which matters in this tool family.

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 only names the 'keyword' parameter with no description. The tool description adds 'single-keyword' to clarify the expected input type, but does not provide examples, formatting rules, or constraints.

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 'Deep single-keyword analysis' and lists the outputs (market metrics, top competitors, seasonality). This distinguishes it from siblings like market_screen or asin_score by focusing on a single keyword.

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?

It provides an explicit use case: 'Evaluating a specific keyword before committing to a product line.' This gives clear context, though it doesn't mention alternatives or exclusions.

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