Install App

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

Annotations (readOnlyHint=false, destructiveHint=false) already indicate this is a mutating operation. The description adds no behavioral details beyond that – it doesn't mention potential side effects (e.g., overwriting existing apps), required permissions, or time expectations. With no annotation coverage on specifics, the description carries the burden and fails to disclose anything extra.

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 a single concise sentence with no filler. It is front-loaded with the core action. However, it is perhaps too brief, missing useful context, but for conciseness alone it earns a 4.

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 mutation tool with no output schema and no usage guidance, the description is incomplete. It doesn't explain the installation flow (e.g., need to allocate a device first), potential impacts, or how to verify success. The schema covers parameters, but broader context is missing, making this inadequate for an agent navigating 30+ siblings.

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% – both parameters have thorough descriptions (path explains platform-specific file types; device references mobile_list_available_devices). The tool description adds nothing beyond the schema, so the baseline of 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?

The description states a clear verb and resource: 'Install an app on mobile device'. It distinguishes from siblings like mobile_launch_app (launch) and mobile_uninstall_app (uninstall) by the action word, though it doesn't explicitly name them. The purpose is unambiguous.

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 guidance is provided about when to use this tool versus alternatives. It doesn't mention prerequisites like device availability or that installation is a prerequisite for launching. The description offers no when/when-not context, leaving the agent to infer from the name alone.

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