xcode_build

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

The description mentions a whitelist constraint ('在白名单项目内'), which is a key behavioral trait. However, with no annotations provided, it fails to disclose other important aspects like side effects (e.g., file creation), permissions required, or error behavior. The agent lacks sufficient transparency to assess safety and impact.

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 a single sentence, which is concise but severely under-specified for a tool with 5 parameters and no schema descriptions. It does not earn its place because it leaves too many gaps that require additional explanation.

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 the tool has 5 parameters, no annotations, no output schema, and no parameter descriptions, the description is far from complete. It omits crucial information about parameter usage, default behaviors, and expected outcomes, making it inadequate for an agent to invoke the tool correctly.

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?

The input schema has 5 parameters with 0% description coverage, and the tool description adds no explanation for any parameter. Critical fields like 'scheme', 'destination', and 'project_path' remain ambiguous. The description fails to compensate for the schema's lack of documentation.

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 executes 'xcodebuild build' and restricts operation to whitelisted projects. It distinguishes from sibling tools like xcode_test and xcode_clean. However, it does not mention key details like the project or scheme being built, leaving some ambiguity about the exact resource.

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 vs alternatives such as xcode_test or xcode_clean. The description lacks explicit context for when it is appropriate or not, relying solely on inference from the tool name.

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