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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that the payload includes status, configuration, and an event cursor, which is useful return-content context. However, it omits error behavior and pagination of the cursor.

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?

One tight sentence that front-loads what is returned. No waste, though it is terse enough that it leaves out potentially useful routing or failure details.

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 usefully names the returned fields, and with full schema coverage the single parameter is covered. Still, for a read against an open-world target it lacks failure-mode or usage guidance, leaving a modest completeness gap.

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% and there is a single UUID-typed autopilot_id, so the schema fully documents the parameter. The description adds no format or semantic detail beyond it, which is the expected baseline when the schema does the heavy lifting.

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 (get) and resource (one autopilot) and clarifies it returns status, configuration, and event cursor. It distinguishes retrieval from the many autopilot mutation siblings (update, delete, start, stop), though it does not explicitly contrast with list_autopilots or get_autopilot_events.

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 explicit when-to-use guidance or prerequisites. The agent can infer it retrieves a single autopilot by ID, but nothing says when to prefer this over list_autopilots or get_autopilot_events, nor what happens if the ID is unknown.

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