install

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

Annotations are not provided, so the description carries the burden of behavioral disclosure. It discloses a 180-second timeout but does not mention whether the operation is destructive or reversible, what side effects occur (e.g., overwriting), or what the response includes. The description adds some value with the timeout but is not rich on behavioral context.

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 sentences, no wasted words, front-loaded with the core action and then the key exception (reinstall) and timeout. Each sentence earns its place.

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?

The description is complete enough for basic usage but lacks context about behavioral side effects, return values, or resolution semantics across the many platforms/selectors. With 18 parameters and no output schema or annotations, a bit more context about expected behavior or failure modes would help. Still, the core operation is simply stated.

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%, so the schema already documents all 18 parameters. The description adds the note about providing an app identifier for explicit app selection, which is useful, but it doesn't go beyond that. Baseline 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 specific verb and resource ('Install an app binary from a local path') and distinguishes itself from the sibling tool reinstall ('use reinstall to replace an already installed app'). It also mentions explicit app selection, which helps an agent identify the tool's purpose clearly.

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?

The description provides guidance on when the app identifier is needed and explicitly routes to reinstall for replacing an installed app. It does not discuss other alternatives like install-from-source or broader platform/device selection context, but the core usage context is clear.

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