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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered and the trailing 'Read-only' is partly redundant. The description still adds genuine value by disclosing the response payload shape and the non-obvious flag semantic 'selected:false means dropped'.

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?

Front-loaded with the core purpose in the first clause, then a dense but information-rich enumeration of payload fields. It is one long run-on sentence, but nearly every clause earns its place by describing a distinct part of the returned record.

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, the description correctly carries the burden of describing return values and does so thoroughly (type, lane, status, error, draft, thread, triage/QA flags, website batch details). The only gap is usage routing relative to approve/hold/reject siblings that share the same id.

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 description coverage is 100% for the single action_id parameter, and the schema already notes the id comes from get_autopilot's queue. The description adds nothing beyond the schema for parameters, so the baseline 3 applies.

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 — fetching ONE autopilot action in full — and explicitly distinguishes it from the queue-level sibling by naming the 'approval card' view and enumerating the fields returned. An agent can tell this apart from get_autopilot without opening either schema.

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?

Usage is implied: it retrieves a single item, and the schema notes the id comes from get_autopilot's queue. However, there is no explicit when-to-use/when-not guidance and no mention of the approve/hold/reject siblings that also act on an action_id.

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