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

Annotations only disclose not read-only, not idempotent, and not destructive, but the description's step list (boot, install, launch) gives a clear picture of the side effects on the simulator. It does not document failure modes or prerequisites like Xcode being installed, but the step list exceeds the annotation coverage and provides meaningful behavioral context.

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 well-structured with a purpose statement, a numbered step list, and a clean required/optional parameter breakdown. It front-loads the core purpose and stays focused, though it is slightly longer than necessary by repeating some schema descriptions.

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?

For a 7-parameter orchestrator with no output schema, the description covers the workflow steps and all parameters sufficiently. It could be more complete by mentioning expected outcomes (e.g., app launches with given arguments) and potential error states, but nothing critical is missing for an agent to safely invoke it.

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 100%, so the baseline is 3. The description adds value by stating the default for takeScreenshot (false) and configuration (Debug already in schema), and by clarifying that environmentVariables is a record of strings and launchArguments is an array (matching schema). It also ties parameters to workflow steps, providing usage context beyond the raw schema.

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 'Build and run an Xcode project on a simulator in a single orchestrated workflow' and enumerates the six steps. It distinguishes itself from the many sibling tools by being the aggregated workflow, not a low-level xcodebuild or simctl call.

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 overview implies this is the go-to for a combined build+boot+install+launch flow, but it never explicitly contrasts with alternatives like xcodebuild-build (build only) or simctl-launch (launch only) or the similar workflow-fresh-install. The 'single orchestrated workflow' phrasing gives context but lacks explicit when/when-not guidance.

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