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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds the ordering guarantee ('newest first') and the status taxonomy, which is useful behavioral context, but says nothing about pagination totals, default page size behavior, or empty-result handling.

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 sentence, front-loaded with the core action, and the parenthetical status list is dense but informative. The inline enumeration of nine statuses is a little heavy but each item carries meaning for interpreting results.

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 carries the return-value burden and does so well, naming ordering, status field, and linked ICP/campaign IDs. It omits pagination metadata (total counts, has-more) that an agent listing paginated results would benefit from.

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?

Both parameters (page, limit) have 100% schema description coverage, including defaults and max. The description adds no parameter-level detail, which is acceptable at this coverage level but earns only the baseline score.

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 ('Lists the workspace's autopilot runs'), adds ordering ('newest first') and enumerates the returned status lifecycle and linked IDs. It is clearly the collection-level counterpart to get_autopilot_run among the listed siblings.

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 by the shape of the tool (browse all runs in the workspace), but there is no explicit guidance on when to prefer this over get_autopilot_run for a single run, nor on how paging interacts with filtering. No alternatives or exclusions are named.

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