hash

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

Description adds 'Read-only, no side effects' aligning with readOnlyHint annotation, and describes output as 'JSON with per-file digests and byte counts'. This is beyond annotations, though more detail on error handling could be included.

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?

Five sentences with every sentence earning its place: purpose, safety, output, usage guidelines, and references. Front-loaded with essential 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?

Covers purpose, safety, output format, and usage guidance. With full schema coverage and no output schema, the description compensates well. Complex encoding parameters are in schema, so complete enough.

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 has 100% description coverage, so description adds minimal parameter semantics beyond mentioning 'selectable algorithm' and stdin support. Baseline score of 3 is appropriate.

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 'Compute hash digests' with specific algorithms (MD5, SHA-1, SHA-2, BLAKE2b) and distinguishes from sibling tools like md5sum, sha256sum, b2sum.

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?

Explicitly says 'Use when you need flexible algorithm selection' and 'Not for fixed-algorithm workflows — use dedicated tools', providing clear when-to-use and when-not-to-use guidance with named alternatives.

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