debug_attach

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

No annotations provided, so description carries full burden. Discloses that breakpoints are armed before target resumes, and that stop_on_entry is simulator-only. However, lacks details on session lifecycle, cleanup, or permissions.

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 concise sentences, each with essential information. No redundancy, front-loaded with purpose and options.

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?

Covers key aspects of usage and breakpoints, but lacks description of return value or session handling. Moderate complexity with 5 parameters, no output schema, so more detail on what 'start a debug session' yields would be beneficial.

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 has 100% description coverage, but description adds value by explaining the mutual exclusivity of bundle_id/pid, the timing of breakpoint arming, and the simulator constraint for stop_on_entry. Enriches beyond 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?

Clearly states it starts a debug session for iOS apps, distinguishes between launching with bundle_id vs attaching to pid, and mentions breakpoints. Differentiates from siblings like debug_breakpoint and debug_detach.

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 provide either bundle_id or pid, and to read reference first. Provides clear context on when to use each parameter, but does not explicitly state when not to use this tool in favor of siblings.

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