ads_keywords

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

No annotations are provided, so the description carries full responsibility. It does not disclose read-only nature, side effects, or output structure beyond mentioning 'performance with quality scores'. Given the lack of annotations, more behavioral detail is needed.

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: a one-line purpose followed by a clear list of parameters. It is front-loaded with the main action. Minor redundancy in repeating defaults but overall efficient.

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 has only 3 optional parameters and an output schema (indicated by context), the description adequately covers purpose and parameter semantics. Return values are not explained, but the output schema likely handles this. Some what-if scenarios are missing but acceptable for this complexity.

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 description coverage is 0%, so the description compensates by explaining each parameter's purpose, format (YYYY-MM-DD), defaults (start_date: 28 days ago, end_date: today, limit: 30), and the role of 'limit' as a max. This adds significant meaning beyond the schema's titles and defaults.

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 the verb 'Get' and the resource 'Google Ads keyword performance with quality scores', making the tool's purpose specific and distinct from sibling tools like 'ads_campaigns' and 'ads_search_terms'.

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 implies usage for retrieving keyword performance but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'ads_campaigns' for campaigns). Defaults for date range and limit are provided but no 'when not to use' information.

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