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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not what is computed (normalized vs. raw entropy, log base), not whether input is parsed as CSV/JSON, not the output shape. Zero behavioral information is provided.

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?

It is short, but shortness here reflects under-specification rather than efficiency; the only content is a duplicated label that consumes space without conveying 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?

No annotations, no output schema, and a one-line tautological description leave the agent without the input format, the entropy variant, or the return value — all of which the description would need to supply given the absent structured metadata.

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 coverage is 100% and the single parameter 'values' is documented as "Values to process". With high schema coverage the baseline is 3, even though the description itself adds nothing about delimiters or expected format.

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?

"Shannon Entropy: Shannon Entropy" merely restates the tool name twice; it names no verb and no resource beyond the concept itself. An agent cannot tell from this text whether the tool computes entropy over a string, a list of probabilities, or a byte stream.

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?

No when-to-use guidance, no alternatives, no mention of related siblings such as x402-entropy, x402-text-entropy, or x402-password-entropy. The agent is left to infer everything from the name.

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