app_install

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action without revealing whether the simulator needs to be running, whether existing installations are overwritten, what errors might occur, or what the tool returns. 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?

Single sentence, no wasted words. Information is front-loaded and direct. Every part of the description earns its place, and it is appropriately short for a simple 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?

For a tool that installs an app bundle, the description omits critical context: expected return value, error scenarios, and post-install state. With no output schema, the description should clarify these aspects. The current brief statement leaves the agent without sufficient information to handle the tool's behavior properly.

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 both 'appPath' and 'deviceId' having adequate descriptions in the schema itself. The tool description does not add any additional meaning or context beyond those field descriptions. Baseline 3 is appropriate; no extra value provided.

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?

Description clearly states the verb 'Install', the resource '.app bundle', and the target 'simulator'. It effectively distinguishes from sibling tools like app_uninstall and physical_device_install by specifying the target environment. However, it could be slightly more precise by clarifying what 'install' entails (e.g., copying to simulator without launching).

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 on when to use this tool vs alternatives like app_launch or physical_device_install. There is no mention of prerequisites (e.g., simulator must be booted), nor any indication of whether it should be used before other operations. The description lacks any usage context.

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