get_entropy

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that entropy is calculated, but does not disclose the return format, whether it is purely read-only, what range the entropy value has, or whether it requires an already-loaded binary session. This is a significant gap for a tool with no annotation metadata.

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 a single concise sentence that front-loads the core action and purpose. There is no wasted phrasing, though the meaning of 'specific sections' could have been made clearer without much additional length.

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?

Given that there is no output schema and no annotations, the description should explain return values and key behavioral context. It also fails to specify default behavior when size or address is omitted, which is critical for an agent to invoke the tool correctly. The description is adequate for grasping the general purpose but not sufficient for correct independent invocation.

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 the parameters are already documented for binary_path, address, and size. The description adds the general concept of 'binary or specific sections' but does not clarify how address and size interact, what happens when they are omitted, or how they relate to section-based entropy calculation.

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 specific action ('Calculate entropy') and the target resource ('the binary or specific sections'), plus the purpose of detecting packed or encrypted regions. It is not a tautology and gives an agent a concrete idea of the tool's role, though 'specific sections' is somewhat ambiguous and does not explicitly differentiate it from sibling analysis tools.

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 when to use the tool: when you suspect packing or encryption and want to measure entropy. However, it provides no explicit guidance on when not to use it, nor does it mention alternative tools like analyze_binary or find_crypto_constants that could also be relevant.

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