hexdump

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

No annotations are provided, so the description carries full burden. It states the tool displays hex/ASCII content and is useful for analysis, but does not explicitly disclose that it is a safe read-only operation or mention file permissions or other behavioral constraints. The output schema exists but is not shown, so some disclosure is still needed.

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?

The description is two sentences, front-loaded with the primary purpose, and provides additional context in the second sentence. It is efficient with no wasted words.

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 the tool's simplicity (2 parameters, 100% schema coverage, output schema exists), the description covers the purpose and typical use cases adequately. However, it could be slightly more complete by comparing with sibling tools like xxd.

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% with both parameters described in the input schema. The description does not add additional meaning beyond what the schema provides; it simply restates that hexdump runs on a file. Baseline 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?

The description clearly states 'Run hexdump on a file to display its contents in hexadecimal format' with a specific verb and resource. It also mentions use cases like analyzing binary formats and file headers, but does not explicitly differentiate from sibling tool xxd which serves a similar purpose.

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?

The description implies usage for binary analysis and raw content inspection, but lacks explicit guidance on when to use hexdump vs alternatives (e.g., xxd, strings). No when-not or alternative tools are mentioned.

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