Get All Resource File Names

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

No annotations exist, so the description carries the full disclosure burden, yet it says nothing about ordering, whether results are paginated, whether 'all' is truly exhaustive, or cost/performance of enumerating an entire APK's resources. Only the existence of an output schema relieves it of explaining the return shape.

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?

One short sentence with no waste and the resource is front-loaded, but the brevity comes from under-specification rather than economy — there is essentially nothing after the core statement.

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 bulk-enumeration tool with two undocumented pagination parameters and zero annotations, the description should at minimum explain paging behavior and the default count=0. The output schema covers return values, but the calling contract remains incomplete.

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 0%, so both parameters (count, offset) are undocumented anywhere. The description does not explain that they paginate the results, nor the unusual default count=0 (which likely means 'everything'), leaving the agent to guess.

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?

Specific verb+resource: 'Retrieve all resource file names' tells the agent this is a bulk listing of resource file names, and 'all' implicitly contrasts with the single-file sibling get_resource_file. However, it never names that sibling or states the distinction explicitly.

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?

There is no guidance on when to use this instead of get_resource_file or get_strings, and no preconditions or exclusions. Usage is only inferable from the word 'all'.

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