get_autopilot

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

With no annotations available, the description carries the full burden for behavioral disclosure. It only says 'Get one autopilot,' which adds no information beyond the tool name itself. It doesn't indicate whether this is a read-only operation, what happens if the autopilot is not found, or any error behavior.

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?

The description is a single sentence with no filler or redundancy. It is appropriately minimal and front-loaded, stating the core purpose in the fewest possible words.

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?

The tool is simple (2 params, no output schema), but the description is too sparse to be considered complete. It doesn't mention the return value, how to handle missing autopilots, or the role of the parameters. Given the lack of annotations and output schema, more context is needed for an agent to invoke it correctly.

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 input schema has 50% description coverage (workspace_id is described, id is not). The description adds no parameter-level insight, failing to explain that 'id' is the autopilot's unique identifier. Without this, an agent may not understand which ID to provide.

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?

The description 'Get one autopilot' clearly states the operation (get) and the resource (autopilot), and 'one' distinguishes it from list_autopilots. However, it is very terse and doesn't explicitly mention that it fetches by ID, though that is implied by the 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?

No guidance is provided on when to use this tool versus alternatives like list_autopilots. It does not mention prerequisites, such as having an autopilot ID, or any exclusions. The usage context must be inferred entirely from the tool name and schema.

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