frida_spawn_app

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

The description discloses the basic behavior (spawn an iOS app) and parameters, but lacks details on consequences like what happens if the app is already running, required permissions, or whether it returns a process object. Without annotations, more depth would be beneficial.

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 extremely concise: a single-purpose sentence followed by a clear parameter list. No unnecessary words or repetition.

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?

Given the tool's simplicity and lack of output schema, the description adequately covers the action and parameters. It does not mention return values or side effects, but this is acceptable for a spawn operation.

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?

The description adds significant meaning to each parameter: explains bundle_id format with example, device_type options with default, and device_id optionality. This fully compensates for the 0% schema coverage.

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 the verb 'spawn' and the resource 'iOS app by bundle ID', making the tool's purpose specific and distinct from siblings like frida_kill_app or frida_resume_app.

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. It simply describes the action without mentioning prerequisites or situations where other tools would be more appropriate.

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