android

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

Annotations indicate non-read-only, non-idempotent, non-destructive, but the description adds that deploy performs export APK, adb install, and optional launch, which is useful behavioral context. However, it does not disclose side effects such as overwriting existing apps or requiring a connected device, so transparency is partial.

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 concise, using a compact action:description list, and front-loads the tool's identity. However, it omits two of the five actions, making the structure incomplete and forcing the agent to consult the schema for full coverage.

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?

With five actions and ten parameters, the description covers only three actions and gives minimal context on parameters or return values. Since there is no output schema, the agent lacks sufficient information about the behavior and results of actions like check_template and logcat.

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 90%, so the parameters are largely self-explanatory. The description only groups actions with their parameters but adds no additional semantic detail beyond what the schema already provides, so it meets the baseline.

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 identifies the tool as 'Android Deploy tool' and lists three key sub-actions (list_devices, get_preset_info, deploy), making its domain clear. However, it omits two actions present in the schema (check_template, logcat) and lacks a single verb-resource summary, so it is not fully comprehensive.

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 explicit guidance is given on when to use this tool versus sibling tools, nor when to select one action over another. The description only implies it is for Android deployment, leaving the agent without clear decision criteria.

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