quest_install

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses two important behaviors: the installed APK replaces an existing install (upgrade) and setting grant_permissions=True auto-grants all runtime permissions. This goes beyond a simple 'install' statement, though it does not cover device selection or error handling.

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 only two sentences and is front-loaded with the primary action. The additional details about upgrade behavior and the grant_permissions flag are concise and valuable, with no unnecessary wording.

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 simple install tool with no annotations and no output schema, this description is adequate but incomplete. It covers the main action, upgrade behavior, and the permission flag, but omits any explanation of device_id, which is important for multi-device environments. It also does not describe return values or failure scenarios.

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 has 0% description coverage, so the tool description must compensate. It explains the grant_permissions parameter fully, but apk_path and device_id are not explained. While apk_path is self-explanatory by name, device_id's optional behavior and default are not clarified, leaving ambiguity when multiple devices are connected.

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 clearly states the tool's function: 'Install (sideload) an APK onto the headset.' This specifies a concrete verb and resource, and the addition of 'Replaces an existing install of the same package (upgrade)' distinguishes it from sibling tools like quest_uninstall and quest_push.

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 gives clear context for when the tool is appropriate (installing an APK) and provides usage guidance for the grant_permissions parameter, specifically noting it is 'useful for test builds.' However, it does not explicitly mention alternatives or when not to use this tool, such as saying to use quest_uninstall for removal.

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