semrush_keyword_ads_history

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

Adds API unit cost information ('100 API units per line'), which is a useful behavioral hint. However, no annotations are provided, so the description carries the full burden; it does not disclose read-only nature or other traits beyond cost.

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?

Single sentence delivering core purpose and cost hint with no extraneous words. Efficient and front-loaded.

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?

Lacks description of output format or return value details. With no output schema, the description should clarify what 'domains' entails (e.g., with metrics, count). Incomplete for a 3-parameter tool.

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% with basic parameter descriptions. The tool description does not add further meaning or examples beyond the schema, so it meets baseline without enhancement.

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?

Clearly states it retrieves domains that bid on a keyword within the last 12 months, specifying the verb, resource, and time constraint. Distinguishes from siblings focused on organic data or overviews.

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 explicit guidance on when to use this vs alternatives like semrush_keyword_paid_results. The description implies historical ad analysis but lacks context for decision-making.

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