patch_manifest_and_config

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

No annotations are provided, so the description must disclose behavior. It lists the exact manifest modifications and mentions a validation status return, which is helpful. However, it does not disclose whether the patch is destructive to existing content (e.g., replacing an existing Application class), required ordering with sibling tools, or failure modes.

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 packs a detailed list of changes and a return value into a single sentence with no redundant or vague filler. It is information-dense and front-loaded.

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 no annotations and no output schema, the description covers what the patch does and that it returns a validation status, but it lacks context about prerequisites, side effects, how the parameters interact, or the validation domain. The moderate complexity of affecting the manifest warrants more context.

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 coverage is 0%, so the description must explain the parameters. It illuminates 'usesCleartextTraffic' and 'customApplicationClass' via the enumerated runtime requirements, but it does not explain 'workspaceDir' (the location of the decoded manifest) or 'additionalPermissions' beyond the INTERNET/WAKE_LOCK permissions. This leaves half the parameters underdocumented.

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 uses a specific verb 'Patch' and identifies the resource 'decoded AndroidManifest.xml', then enumerates concrete changes (permissions, Application class, activity_overlay, metadata). This clearly distinguishes it from sibling tools like inject_flutter_runtime_and_smali or recompile_align_and_sign.

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 usage after decoding and before recompiling, but it does not explicitly state when to use this tool versus siblings or any prerequisites/exclusions. It defines the tool's role by its object, but not decision guidance.

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