md5sum

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

Confirms read-only, no side effects, matching annotations. Discloses output format (JSON with hash values and byte counts) and warns about MD5 security weakness, adding value beyond annotations.

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?

Three sentences, front-loaded with action. No redundant information; each sentence serves a purpose: action, nature, output, usage guidance, and warnings.

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 6 parameters (all described in schema) and no output schema, the description adequately explains output and use cases. Provides critical security warning and links to alternatives, making it complete for its complexity.

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%, so baseline is 3. Description adds context like 'or '-' for stdin' and 'Read checksums from FILE(s) and verify them', improving understanding beyond schema.

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?

Specifies action 'Compute MD5 hash digests' with resource 'files or stdin'. Distinguishes from siblings by noting security differences and naming alternatives like sha256sum and 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 states when to use ('fast non-cryptographic integrity checks, data deduplication') and when not to use ('Not for security or cryptographic verification'). Recommends alternative tools for security.

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