xcode_test

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

No annotations are provided, and the description only states the action 'execute xcodebuild test'. It does not disclose potential side effects, required permissions, or what happens if the project is not in the whitelist.

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 under-specified. It lacks essential details, making it insufficiently informative.

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 5 parameters with no schema descriptions, no output schema, and no annotations, the description is critically incomplete. It fails to explain return values, whitelist behavior, or parameter usage.

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?

All 5 parameters have no descriptions in the schema (0% coverage), and the description adds no meaning to the parameters. The agent has no guidance on what values to provide for scheme, xcode_path, destination, project_path, or configuration.

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 it executes xcodebuild test on whitelist projects, distinguishing it from sibling tools like xcode_build. However, the term 'whitelist projects' is undefined, and the Chinese language may reduce clarity for some agents.

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 on when to use this tool versus alternatives like xcode_build, nor any prerequisites or constraints mentioned (e.g., project must be in whitelist).

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