xcodebuild_list

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

No annotations are provided, so the description must disclose behavioral traits. It fails to state that the operation is read-only or that inputs must exist, assuming typical inference but insufficient for robust agent use.

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 two short sentences plus Args/Returns stanzas. Every part is valuable, and the key action (list) is front-loaded.

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's simplicity, the description covers the return value type. It omits potential errors or prerequisites but is largely sufficient. An output schema exists, so return details are not needed.

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 coverage is 0%, but the description adds basic meaning by labeling each parameter as 'Path to .xcodeproj file' and 'Path to .xcworkspace file'. However, it does not explain constraints like mutual exclusivity or optionality beyond what schema defaults imply.

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 explicitly states the tool lists targets and configurations for projects or schemes for workspaces, clearly distinguishing its purpose from sibling tools like xcodebuild_build or xcodebuild_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?

The description implies when to use (listing), but lacks explicit guidance on when not to use or mention of alternatives. It does not clarify that project and workspace are mutually exclusive, leaving room for misuse.

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