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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely useful behavior: rules are evaluated hourly, and each carries a mode whose semantics are spelled out (dry_run records intentions, live acts, off is inert) plus a last-checked timestamp. It stops short of saying whether rules are paginated, sorted, or limited in count.

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?

A single front-loaded sentence with the resource first, followed by parenthetical elaboration on modes. The example rule earns its place by making 'standing order' concrete. The embedded parenthetical is slightly dense but nothing is redundant.

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 output schema and no parameters, the description carries the burden of explaining what comes back — and it does, naming three returned fields (plain-words description, mode, last checked). For a zero-argument read of a small rule set, this is close to sufficient; only result ordering or volume expectations are missing.

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 baseline is 4 and there is nothing for the description to compensate for. The description spends its words on return content instead, which is the appropriate trade-off here.

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 concrete resource — the account's autopilot rules — and even gives an example of what a rule looks like ('pause any ad set that spent R200 with no purchases in 3 days'), so an agent knows this returns standing-order definitions rather than, say, change history. It does not explicitly contrast itself with create_autopilot_rule or list_changes, so sibling differentiation is only implied by the plural-read framing.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative; the agent must infer that this is the inspection counterpart to create_autopilot_rule. The 'checked every hour' detail hints at monitoring use cases but never states a selection condition.

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