google_ads_dismiss_recommendation

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

No annotations provided, so description carries full burden. Only states that dismissal removes from list; lacks disclosure of irreversibility, permissions, or effects beyond removal. For a write operation, more 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?

Description is concise with no filler. Header, usage sentence, then Args/Returns/Example. Information is front-loaded and well-structured.

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?

Tool is simple; description covers purpose, usage, and return. Lacks mention of bulk alternative or whether dismissal is reversible, but given the tool's narrow scope, it is largely complete.

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 has 0% description coverage; description adds 'without hyphens' for customer_id and clarifies recommendation_resource_name as resource name. Example provides format. Adds value but could detail naming conventions 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?

Description clearly states the action (dismiss) and resource (recommendation), and distinguishes from applying recommendations, which is a sibling tool. The purpose is unambiguous.

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?

Explicitly states when to use: 'when you don't want to apply a recommendation and want to remove it'. Provides clear context but does not mention bulk alternative (google_ads_bulk_dismiss_recommendations) present among siblings.

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