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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false. The description adds real value with the auth requirement ('Admin only') and the effect ('Notify after hourly sync; does not pause'), but for a destructive 33-parameter mutation this is thin, and 'does not pause' sits in some tension with the declared destructive/idempotent hints.

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?

Three short sentences, action stated first followed by constraints. Every sentence adds something (operation, auth, effect) with no filler, though the brevity is very aggressive for a 33-param tool.

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?

This is a high-complexity tool (33 params, 0% schema coverage). The description does not document parameter roles or the create-vs-update distinction (rule_id, action, condition, etc.), leaving the agent without enough to build a correct call. The output schema does cover return values, so that is not a gap.

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% across 33 parameters, so the description must carry the burden. It provides no parameter names or meaning at all — only the tangential 'notify/does not pause' behavioral hints — so it fails to compensate for the coverage gap.

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 states a specific verb and resource ('Create or update an ads alert rule'), and the 'ads' qualifier distinguishes it from the sibling seo/automation upsert tools. It does not, however, explicitly name or route away from those alternatives.

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?

'Admin only' communicates a permission prerequisite, which is useful context. But there is no guidance on when to use this versus automate_upsert_automation_rule or automate_upsert_seo_alert_rule, so usage is only implied.

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