framework

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

Annotations already flag destructiveHint=true and openWorldHint=false, and the description adds substantive context beyond that: only pre-configured fixed CLIs are invoked, nothing is auto-installed, and the Blutter download/build path is explicitly gated. That materially reduces the risk of an agent triggering an unexpected install or build.

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?

Three short sentences with no filler, and the capability list is front-loaded ahead of the constraints. It reads dense but every clause carries information.

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 destructive, five-parameter tool with no output schema and zero schema coverage, the description covers safety and engine identity but omits what analyze actually does, what path/metadataPath refer to, and what the caller receives back. Enough to avoid misuse of the build path, not enough to call the tool confidently.

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 the description must carry parameter meaning. It does partially: the engine names map to the engine enum and allowEngineBuild is tied to Blutter, but path, metadataPath, and the difference between the action values probe and analyze are left entirely unexplained.

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 names the three operations (list engines, probe, analyze) and enumerates the concrete engine set (Hermes, Blutter, ILSpy, GDRE, IL2CPP, Ark), so an agent knows what the tool operates on. It does not, however, distinguish this tool from siblings such as 'native', 'decode', or 'frida', which could plausibly touch the same targets.

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?

It gives a genuine precondition — Blutter requires explicitly allowing download/build via allowEngineBuild — which is real when-to-use guidance. But it never says when to choose probe vs analyze, or when this tool is preferable to the decode/native/frida siblings.

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