xcodebuild_build

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

No annotations exist, and the description only states 'Build' without disclosing behavioral traits like duration, side effects (e.g., generated artifacts), or failure conditions. Minimal transparency beyond the obvious.

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 concise with well-structured bullet points for arguments. However, the 'Returns' line is redundant if an output schema exists, and space could be used for more value-added content.

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?

Given 8 parameters and no annotations, the description covers basic parameter names but lacks depth. No explanation on choosing between mutually exclusive options (project vs workspace) or environment prerequisites.

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?

With 0% schema description coverage, the description provides basic parameter explanations (e.g., 'Path to .xcodeproj file'). These add minimal meaning but lack details like allowed values, constraints, or relationships between parameters.

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 clearly states the tool builds an Xcode project or workspace, with a specific verb and resource. It distinguishes from siblings like xcodebuild_archive (archive) and xcodebuild_test (test).

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?

No guidance is provided on when to use this tool versus alternatives, nor on how to choose between project/workspace or scheme/target. Missing prerequisites or context for when building is appropriate.

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