install

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

No annotations are provided, so the description carries the full burden. It discloses the local-path nature and hints that reinstall is for replacement, but it does not explain installation behavior such as overwriting, prerequisites, permissions, failure modes, or return values. For a mutating operation, this is a notable gap.

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 two sentences, front-loaded with the primary purpose, and every phrase adds value. It is concise without being under-specified.

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 schema is rich and covers parameter details, but there is no output schema and no annotations. The description provides the core scenario and the reinstall alternative, but lacks behavioral context such as what happens if the app already exists, whether installation is non-destructive, or what output to expect. Adequate but not complete for a mutating tool.

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 schema descriptions cover all 26 parameters, so the baseline is 3. The description adds a meaningful clarification for the 'app' parameter (use it when explicit app selection is needed), but does not improve understanding of the other parameters beyond the schema.

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 action ('Install an app binary from a local path') and clearly distinguishes it from the sibling 'reinstall' by noting that reinstall replaces an already installed app. It also implies a distinction from 'install-from-source' by emphasizing a binary path.

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?

Provides clear context for when to use the tool (installing a local binary) and explicitly directs to 'reinstall' for replacing an installed app. It does not enumerate all possible alternatives but gives a key exclusion, making usage guidance solid.

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