reinstall

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Reinstall an app binary' without mentioning whether it is destructive (e.g., clears app data), requires prior installation, or any side effects. This is insufficient 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?

The description is a single sentence, which is concise, but at 23 parameters, it is too terse. It is front-loaded but lacks structure to convey essential context. Some brevity is acceptable, but more detail is needed for such a complex tool.

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 complexity (23 parameters, no output schema, no annotations), the description is grossly incomplete. It fails to explain what 'reinstall' entails (e.g., does it uninstall first?), the types of apps, or any expected results. The agent would be left guessing.

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 96%, so most parameters are documented in the schema. The description adds no additional meaning beyond that. With high coverage, a baseline of 3 is appropriate, though the description could have highlighted critical parameters like 'appPath'.

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 'Reinstall an app binary' clearly states the action and resource (verb+resource), but it does not differentiate from sibling tools like 'install' or 'install-from-source', which could also install an app binary. The purpose is clear but lacks specificity to distinguish it.

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 no guidance on when to use this tool instead of alternatives. With many sibling tools for app management, such as 'install', 'install-from-source', and 'replay', an agent has no context to choose 'reinstall' over others.

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