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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write-capable nature is known. The description adds two genuinely useful behaviors beyond that: completed steps are skipped and there is a 2-per-hour cap. It does not say what the run produces, whether it publishes content, or what happens when the rate limit is hit, so the transparency gain is real but partial.

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?

Two short sentences with no filler. The primary action and its timing rationale are front-loaded, and the caveats about skipped steps and rate limiting follow compactly.

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, no output schema, and annotations covering the safety profile, the description supplies most of what an agent needs: trigger intent, timing, idempotent skipping, and a rate limit. It leaves out what the run actually does downstream and what the response looks like, which are modest gaps for a zero-arg tool.

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. The description correctly implies no arguments are needed and adds no misleading parameter guidance.

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 ('trigger a manual autopilot run') plus the distinguishing timing ('immediately instead of waiting for the nightly run'). It is clear what the tool does, though it does not explicitly name a sibling such as list_autopilot_runs or configure_autopilot for contrast.

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?

Gives clear context for when to call it: when you want the run now rather than waiting for the scheduled nightly execution. It stops short of naming alternatives or stating exclusions, so it sits at clear-context guidance rather than full when/when-not routing.

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