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

It adds real behavior beyond the annotations by disclosing that the guardrail cap and cooldown still apply even on a manual trigger. However, with destructiveHint=true and readOnlyHint=false, the description never says that the rules being evaluated may actually mutate campaigns, budgets or statuses — a caller reading 'evaluate ... and report what fired' could reasonably assume a dry run.

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, each earning its place: what it does, the constraint that still binds, and the intended use case. The most decision-relevant information (manual trigger vs schedule) is 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?

With no parameters and no output schema, the description must carry the return-value burden, and 'report what fired' is the only hint at what comes back. For a destructive, side-effecting execution tool it should also spell out whether actions are actually applied and what a caller should check afterward.

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 tool takes zero parameters, so the schema imposes no semantic burden and the baseline of 4 applies. The description correctly implies a global run with no scoping options, which is consistent with the empty, additionalProperties=false schema.

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?

States a specific verb and resource ('Evaluate your active rules') plus the triggering mode ('right now instead of waiting for the schedule'), which cleanly separates it from list_automation_rules, create_automation_rule and set_automation_rule_active in the sibling set.

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 'instead of waiting for the schedule' clause and 'Useful for testing' give a clear condition for choosing this over the normal scheduled path. It stops short of stating exclusions or naming sibling tools such as list_automation_rules for pure inspection, so it is clear context rather than a full routing rule.

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