list_apks

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It implicitly indicates a read-only operation via 'List', but does not explicitly state safety aspects, error behavior, pagination, or any limitations. For a simple listing, this is adequate but leaves room for more transparency.

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, concise sentence that states exactly what the tool does without any superfluous information. It is front-loaded and efficient, earning full marks for conciseness.

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 simplicity (one parameter, output schema exists), the description is minimal but functional. However, it lacks any usage guidance and does not mention whether results are paginated or if there are any limits. While not critical for a basic list operation, the absence of such context makes it average rather than complete.

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 covers 100% of the parameter documentation (package_name described as 'App package name'). The description adds no additional meaning beyond the schema, merely repeating 'for an app'. With high schema coverage, the baseline is 3, and the description does not exceed that.

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 with a specific verb ('List') and resource ('APKs'), scoped to 'currently uploaded for an app'. It implicitly distinguishes from sibling tools like list_generated_apks (which likely lists system-generated APKs) and list_bundles, making the purpose specific and unambiguous.

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 versus alternatives. It doesn't mention any exclusions or prerequisites, nor does it reference sibling tools like list_generated_apks or list_bundles. There is no context indicating scenarios where one might prefer another listing tool.

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