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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=false, so the safety profile is covered. The description adds one real behavioral fact beyond the annotations (no automation session needed), but omits whether an existing install is overwritten, whether the device must be unlocked/trusted, or any error conditions for a mutation tool.

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?

Two short sentences, zero filler, with the core action front-loaded and the session caveat immediately after. Nothing could be trimmed without losing information.

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 two-parameter tool with a complete schema and annotations covering the safety profile, the description supplies the essential action plus the session-free usage note. A brief note on reinstall/overwrite behavior would close the remaining gap, but nothing critical for invocation is missing.

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 description coverage is 100% with only two required parameters (path, udid), both fully documented in the schema. The description adds no syntax, format, or constraint details beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb (install) and resource (IPA or .app on an iOS device), which is more precise than the generic sibling app_install. It does not explicitly contrast itself with app_install or ios_uninstall_app, but the iOS-specific artifact types make its domain clear.

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 automation session required' implies a usage context (callable outside a session), which is genuinely useful routing information. However, it gives no explicit guidance on when to prefer this over app_install, app_upload, or ios_launch_app, leaving alternatives to inference.

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