inject_flutter_runtime_and_smali

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that it returns a 'detailed patch report' and lists what it generates, including optional components. However, it does not mention side effects such as modifying the workspace tree in-place, or any required permissions or prerequisites beyond the decompiled APK. This is adequate but not fully transparent for a mutation tool.

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 three sentences, front-loaded with the main purpose, and every sentence contributes meaningful detail (what is injected, what is generated, and the return report). There is no redundant or filler text; it is appropriately sized for the tool's complexity.

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?

Despite naming several generated artifacts and the return report, the description omits critical context: it does not explain what payloadDir should contain, the meaning of the injection mode enum, or how this tool fits into the overall pipeline (e.g., that it requires a decompiled APK from decompile_apk and precedes patch_manifest_and_config). With no output schema and five parameters, the description is incomplete for a complex injection tool.

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%, and the description explains none of the parameters (workspaceDir, payloadDir, engineId, injectionMode, methodChannelBridge). It only incidentally mentions 'activity_overlay mode' without explaining the full enum or other fields. The description adds virtually no meaning beyond the raw schema, failing to compensate for the lack of parameter documentation.

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 starts with a specific verb and resource: 'Inject Flutter engine assets, native libraries, and Smali glue code into a decompiled APK tree.' It clearly states what the tool does and enumerates the generated artifacts (InjectedApplication, cached-engine bootstrap, optional overlay activity, optional bridge), distinguishing it from sibling tools like decompile_apk 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 the tool is run after decompilation ('into a decompiled APK tree') but does not explicitly state when to use it versus alternatives, mention prerequisites, or indicate exclusions. The usage context is only implied, with no direct guidance such as 'run after decompile_apk' or 'when you need to inject a Flutter runtime.'

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