set_run_destination

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

Annotations confirm idempotentHint=true, and description adds effect on subsequent build/run. However, does not disclose error handling for invalid destination_id or project_path.

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?

Three sentences plus docstrings for args/returns; front-loaded purpose, no extra 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?

Explains dependencies (list_run_destinations), effect on subsequent operations, and return format. Has output schema, so return explanation is adequate.

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 description provides full explanations for both parameters: project_path as path to .xcodeproj/.xcworkspace, destination_id as ID from list_run_destinations with UDID example.

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?

Clearly states 'Set the active run destination' with specific verb and resource. Distinguishes from sibling tools like list_run_destinations and get_active_run_destination.

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?

Explicitly instructs to use list_run_destinations first to get destination IDs, then pass the id here. Implies usage context before build/run operations, but no explicit when-not-to-use.

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