xcode_debug

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

The description warns that debugging can run indefinitely and not to timeout, which is a critical behavioral note. However, it omits other behavioral details such as that it launches the app, waits for breakpoints, or requires stopping via xcode_stop.

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?

Extremely concise: two sentences. First explains purpose, second adds a critical warning. No wasted words, 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?

For a debugging tool that launches a session, the description lacks details about the debugging process, output, how to interact, and the relationship with other tools like xcode_stop. Incomplete for the complexity of debugging.

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?

Input schema already covers all parameters with descriptions. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 specifies 'Start debugging session' for a project, which distinguishes it from build, test, and other sibling tools. However, it could elaborate that this launches the app with a debugger attached.

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 explicit guidance on when to use this tool versus alternatives like xcode_build_and_run or xcode_test. The only usage note is about indefinite runtime, but no context for appropriate use cases.

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