img_entropy_map

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

No annotations are provided, so the description carries the full burden. It discloses the algorithm steps (splitting into blocks, calculating entropy, flagging high-entropy regions) but does not mention the output format, whether it returns an image or data, or any side effects. The mutability is implied as read-only but not stated.

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 two sentences, concise and without fluff. It efficiently conveys the purpose and method. However, it could benefit from a slightly more explicit structure, such as indicating the output type.

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?

With no output schema, the description should at least hint at the return format (e.g., a heatmap image, coordinates list). It only says 'flagging high-entropy regions' without specifying how. Additionally, no information about supported image formats or error handling is provided. The tool's context is moderately covered.

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 100%, so baseline is 3. The description adds context that block_size controls the size of blocks for entropy calculation but does not add significant semantics beyond what the schema already provides for the two parameters.

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 performs per-block entropy analysis on an image, calculating Shannon entropy and flagging high-entropy regions. It uses a specific verb-resource combination and distinguishes itself from sibling tools like file_entropy (overall file entropy) and img_chi_square (chi-square analysis).

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 for detecting hidden data via entropy analysis but does not explicitly say when to use this tool versus alternatives like img_lsb_detect or img_rs_analysis. No when-not or alternative guidance is provided.

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