cyberchef_entropy

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

With no annotations, the description carries the full burden and does well: it discloses concrete behavioral facts — the alphabet-dependent ceilings (Hex 4.0, Base64 6.0, Raw 8.0 bits/char) and the four returned metrics. It stops short of stating that the operation is pure/side-effect-free or how the alphabet is auto-detected, but the computational, non-mutating nature is evident.

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, front-loaded with the core operation before the interpretation guidance. The list of four return fields is dense but each one is informative; minor trimming possible but nothing is wasted padding.

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 compensates by naming the returned fields (bitsPerChar, maxForAlphabet, normalizedRatio, totalBits) and the interpretation thresholds. Together with the single well-documented parameter, an agent has enough to call and interpret the tool; only the alphabet-selection mechanism is left implicit.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents 'input' fully. The description adds the notion of alphabet variants but never explains how the single string parameter relates to Hex/Base64/Raw detection, so it adds little parameter-level meaning beyond baseline.

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 opens with a specific verb+resource ('Calculates Shannon entropy and saturation') and immediately scopes it against alphabet ceilings. No sibling tool computes entropy, so the agent can distinguish it instantly from cyberchef_magic or cyberchef_bake.

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 states the analytical context clearly ('to accurately determine whether data is plaintext, compressed, packed shellcode, or high-entropy ciphertext'), which tells the agent when this is the right tool. It does not, however, name alternatives or state when not to use it (e.g., for short inputs where entropy is unreliable).

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