upload_apk

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

The description discloses key behaviors: it creates a new edit, commits the upload, and is disabled in read-only mode. However, with no annotations, it does not mention potential side effects (e.g., overwriting, impact on existing versions) or permissions beyond the read-only note.

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 and well-structured: a single sentence stating the action and a conditional note. No unnecessary words or repetition.

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 description covers the essential behavior and condition. Since an output schema exists, it does not need to explain return values. It lacks some context (e.g., prerequisites) but is adequate for a simple upload operation.

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 input schema provides clear descriptions for both parameters (apk_path and package_name), achieving 100% schema coverage. The tool description adds no extra semantic detail, so the baseline score of 3 is appropriate.

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 action: 'Upload an APK to a new edit and commit it.' This is specific (verb+resource) and distinguishes it from other upload tools (e.g., upload_bundle).

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 the action but does not explicitly state when to use it over alternatives. The 'Disabled in read-only mode' is a condition, not a usage guideline. Lacks explicit context for when this tool is appropriate.

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