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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond annotations: ordering (newest first) and the concrete set of status values a run can carry. It omits pagination behavior and total counts, so it is not exhaustive.

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?

It is a single dense sentence that front-loads the core action and then the return details. Every clause carries information the agent can use; the status enumeration is justified because there is no output schema.

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 must describe return values, and it covers ordering, status, and correlation IDs. Parameter semantics are in the schema. It falls short of complete only in not mentioning pagination metadata or what a caller should do when there are many runs.

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%: page and limit are both documented in the schema, including default 50 and max 200. The description adds nothing about these parameters (for example, that default paging may truncate long lists), so the baseline of 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?

The description states a specific verb (lists) and resource (the workspace's autopilot runs) and adds scope details: newest-first ordering, the status values returned, and linked ICP/campaign IDs. An agent can distinguish this from get_autopilot_run, which fetches a single run, 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?

The intended use (enumerate workspace autopilot runs) is implied by the wording, but the description gives no explicit when-to-use guidance, no exclusions, and no routing to sibling tools such as get_autopilot_run for detail or kill/pause/approve for mutations. The guidance is adequate but incomplete.

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