Build an Xcode project or workspace

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

With no annotations, the description carries the burden of behavioral disclosure. It states the core action and workflow placement, but does not mention build outputs, side effects, or failure behavior. This is a reasonable baseline for a straightforward build command, but it leaves some behavioral detail undisclosed.

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?

The description is two concise sentences with no wasted words. It front-loads the action, then provides workflow context and prerequisites. Every sentence earns its place.

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?

The tool has six parameters, no annotations, and no output schema, but the description only covers scheme and the project/workspace relationship. It omits guidance for destination, configuration, and derivedDataPath, and does not describe what the build returns or how failures are reported, leaving an agent under-informed for non-default invocations.

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 0%, so the description must compensate for undocumented parameters. It clarifies that scheme is required and that project and workspace are alternatives, but it does not explain destination, configuration, or derivedDataPath, leaving half the parameters semantically uncovered.

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 and resource: 'Run xcodebuild build for a project or workspace.' It clearly identifies the build action and differentiates it from sibling tools like install_app and launch_app by positioning it as the step before installing and launching.

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?

It gives clear context on when to use the tool: 'Use before installing and launching the app.' It also states the key prerequisite of requiring a scheme and either a project or workspace, though it does not explicitly name alternatives or exclusion conditions.

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