decode_manifest

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

Without annotations, the description carries full behavioral transparency. It explains the output format (text + parsed lists), and discloses error handling for binary-only manifests, stating that errors are surfaced rather than silently returning partial results. However, it does not discuss permissions, side effects, or read-only nature explicitly.

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 with three short paragraphs covering purpose, return value, and error handling. It avoids redundancy and is front-loaded with the main action. Minor improvement could be made by structuring the list of returned elements more compactly.

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 tool with one parameter, no output schema, and no annotations, the description provides adequate context: what it does, what it returns, and how it handles failures. It lacks details on path format or prerequisites, but overall it is sufficiently complete for an experienced analyst.

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 has one required parameter 'path' with no description in the schema (0% coverage). The tool description does not explain what 'path' refers to (e.g., file path on the system), leaving the agent to infer its meaning. This lack of detail hampers correct parameter specification.

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 decodes the APK's AndroidManifest.xml and returns text and parsed component lists. It uses a specific verb ('Decode') and resource ('APK's AndroidManifest.xml'), distinguishing it from sibling tools that focus on other APK analysis tasks.

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 implies use when decoding the manifest, but does not explicitly state when to use this tool versus alternatives (e.g., parse_apk). It mentions a fallback to apktool d for binary-only manifests, providing some context, but lacks clear when-not guidance.

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