pwntools_entropy

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat safety. It adds behavioral context (Shannon entropy) but does not elaborate on output format or performance. No contradiction.

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?

Two sentences: first states purpose, second gives use-case. No fluff, front-loaded, every sentence earns its place.

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 simple computation tool with annotations covering safety and output schema expected to define return values, the description is mostly complete. It could mention the output range or format, but the use-case context is sufficient.

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 explain parameters. However, it only mentions 'file or memory region' without detailing the 'path', 'size', or 'offset' parameters. No parameter information is added beyond what the schema (which lacks descriptions) provides.

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?

Description clearly states the tool calculates Shannon byte entropy of a file or memory region. The verb 'calculate' is specific, and the resource is well-defined. It distinguishes itself from sibling tools like pwntools_hexdump or pwntools_elf_read, which do not calculate entropy.

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?

Description provides context on when to use: detecting encryption, packing, or embedded data. It does not specify when not to use or mention alternatives, but the use-case is clear and helpful.

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