List Xcode Cloud workflows

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the purpose sentence — no pagination expectation, no note that results are limited/token-scoped, and no hint of what a workflow record contains, so mutation/behavior context is essentially absent.

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?

A single front-loaded sentence with zero filler. It is efficient, though its terseness is part of why other dimensions are thin rather than a structural flaw of its own.

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?

For a low-complexity read-only paginated list tool with full schema coverage and readOnly annotations, the description is minimally viable. However, with no output schema, the description gives no indication of what a workflow object contains, leaving a modest 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 description coverage is 100%, with limit, cursor, and productId all documented in the schema, so the schema carries the full burden. The description adds no additional parameter meaning (e.g., typical limit values or pagination semantics), making the baseline 3 appropriate.

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 (list workflows) plus a clear scope: they belong to a single Xcode Cloud product, which maps to the required productId. An agent can tell it apart from list_ci_products and list_ci_build_runs from the noun alone, though the description never names those siblings explicitly.

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 description gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as list_ci_products (to obtain a productId) or list_ci_build_runs. Usage is only inferable from the schema's productId note.

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