xcode_build_and_run

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

Adds key trait 'Can run indefinitely - do not timeout' beyond schema, but lacks details on auth, destructive effects, or other behaviors. No annotations to rely on.

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?

Two concise sentences, front-loaded with purpose. Emoji adds visual cue. No unnecessary words.

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?

Missing output schema and annotations. Description does not explain return values, error conditions, or prerequisites beyond runtime warning. Incomplete for a complex tool.

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 covers 100% of parameters with adequate descriptions. Description does not add extra semantic meaning beyond what schema already provides.

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?

Description clearly states it builds and runs a project with a specified scheme, using specific verbs and resource. Differs from siblings like xcode_build (build only) and xcode_debug.

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?

Implies usage when needing to build and run, but no explicit guidance on when to use alternatives or prerequisites. Missing exclusions like 'use xcode_build if only build needed'.

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