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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is low, yet the description adds essentially nothing useful and instead asserts 'the four live agents running on a schedule' — a scope claim that the status/archived parameters below it undermine.

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 short sentence with no filler and no buried preamble. It is efficient, though the brevity comes at the cost of substance rather than by editing out redundancy.

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?

For a simple two-optional-parameter read tool with no output schema, the description should at minimum clarify scope and usage, but it leaves out when to use it and gives a misleading impression that only running scheduled agents are returned.

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 coverage is 100%, so the parameters are already documented, but the description's framing ('four live agents running on a schedule') actively narrows the implied scope in a way that conflicts with the status filter and the archived flag, which is worse than adding nothing.

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?

It implies a listing of the account's autopilots, and the singular sibling get_autopilot gives some contrast, but no explicit verb is used and the qualifier 'the four live agents running on a schedule' is strangely narrow and hard to reconcile with the filtering options. An agent gets the gist but not a clean, precise statement of scope.

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?

No when-to-use guidance at all, despite many plausible alternatives in the sibling list (get_autopilot, autopilots_analyses, autopilots_logs, autopilot_action). Nothing tells the agent when to reach for this versus a more specific autopilot tool.

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