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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), and the description adds useful workflow context beyond that: the returned items are unapproved draft launches and must be edited through update_launch before being acted on. It does not discuss ordering or pagination behavior, but those are minor for a read-only list.

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, zero filler, and the key scoping fact ('awaiting approval') is front-loaded. The second sentence carries genuinely actionable information rather than restating fields.

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 no-required-param, read-only list tool with a fully documented schema and no output schema, the description covers what the items are (draft launches) and what to do with them. A brief note on ordering or total count would make it fully complete, but nothing critical is 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?

Schema coverage is 100% with both pagination parameters fully documented (defaults, min/max, page_size cap of 50). The description adds no meaning about them, so the baseline 3 applies since the schema does all the work.

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 ('list autopilot drafts awaiting approval') and narrows the scope with '(review mode)' plus the clarification that each item is a draft launch. That distinguishes it from the plain list_launches and list_autopilot_runs siblings without needing to name them.

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: you want drafts sitting in review mode, and the follow-up actions are approve, reject, or edit. It explicitly names update_launch as the edit path, though it does not name approve_autopilot_draft or reject_autopilot_draft as the corresponding siblings, so routing on the approve/reject steps is left implicit.

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