profile_launch

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

No annotations provided, so the description covers behavioral aspects well: it mentions recording and analysis, and the importance of launching via launch_path. Could add details on device impact or side effects.

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?

Concise with no fluff, front-loaded purpose, and structured bullet points. Could be more structured but efficient.

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 the two main modes, return values, and key caveats. No output schema provided, but description compensates. Lacks error handling or examples but adequate for complexity.

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% with descriptions, but description adds logical grouping (launch_path vs trace_path), default for duration, and clarifies that launch_path is logically required unless trace_path is used.

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 'Record and analyze app launch performance' and lists specific return values. It distinguishes from sibling tools like profile_cpu or analyze_trace by focusing on launch-specific metrics.

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 states when to use launch_path vs trace_path, and warns that attaching to a running process won't work. Provides clear guidance on re-analyzing existing traces.

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