Get Xcode Cloud build

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 genuine context beyond that by disclosing the response shape — a run plus each of its actions and their results — which matters because there is no output schema. It does not cover failure modes for an invalid ID or whether artifacts/logs are included.

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. The resource and the returned payload are stated up front, and nothing is repeated from the schema or annotations.

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 one-parameter read tool with full schema coverage and annotations declaring read-only behavior, this is nearly complete; the description helpfully compensates for the missing output schema by naming the returned actions. Only the error/empty behavior for an unknown buildRunId is left unaddressed.

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%, and buildRunId already documents its origin ('from list_ci_build_runs'). The description adds no meaning beyond the schema, so the baseline 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?

States a specific verb and resource ('Gets an Xcode Cloud build run') and even enumerates the action types returned (build, test, analyze, archive). It is clearly a single-item fetch distinct from list_ci_build_runs, but it never names the sibling, so the differentiation is inferred from singular-vs-plural naming rather than stated.

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 only implied: needing one build run by ID. There is no explicit when-to-use guidance, no mention of when to prefer list_ci_build_runs, and no prerequisites. The only routing hint ('from list_ci_build_runs') lives in the schema, not the description.

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