List Xcode Cloud builds

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the only behavioral fact not in structured data: results are returned newest first. It says nothing about pagination behavior beyond the cursor param itself, nor about result volume or throttling.

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?

Two short sentences, zero filler, with the scope and the key parameter requirement front-loaded. Every clause carries information.

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 read-only, fully-documented list tool this is close to adequate, but the biggest practical ambiguity — behavior when both or neither of workflowId/productId are passed, since all params are optional — is left unresolved for the agent.

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%, so each parameter is already documented with its source (list_ci_products, list_ci_workflows). The description's only added meaning is the either/or relationship between workflowId and productId, which the schema does not state — useful but minimal.

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?

"Lists Xcode Cloud build runs for a workflow or a whole product, newest first" names a specific verb, resource, scope, and result ordering. The phrase "Xcode Cloud build runs" separates it from list_builds (TestFlight builds) and get_ci_build_run (single build), though it 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?

"Pass workflowId or productId" implies the two mutually exclusive scoping modes, which is real usage guidance. However, it does not say what happens if both or neither are supplied (all four params are optional per schema), nor when to prefer get_ci_build_run over this tool.

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