webdev_hex_viewer

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

Annotations provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds critical behavioral context beyond annotations: 'Runs locally on the data you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/minute for anonymous callers).' No contradiction is present.

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 appropriately sized and front-loaded: it starts with the core functionality, then lists output features, usage guidance, and safety notes. Every sentence adds value, and the structure is logical without redundancy.

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 complexity (3 parameters, nested object, output schema), the description covers purpose, usage, behavior, and output components. It mentions the output fields (hexDump, totalBytes, byteDistribution, fileTypeHint) without needing to detail them further due to the presence of an output schema. It is complete and self-contained.

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 description coverage is 100%, so baseline is 3. The description adds context about input decoding methods (text, hex, base64) and mentions that blank input yields an empty dump, but does not significantly enhance parameter understanding beyond the schema. The description also summarizes output fields, which is helpful but not directly about parameters.

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 the tool's purpose: 'Hex Viewer And Binary Analyzer' that produces a hex dump with offset, hex bytes, ASCII gutter, byte statistics, frequency distribution, and file-type hint. It explicitly distinguishes itself from sibling tools such as webdev_base64_image_encoder and encoding_decoding tools, specifying alternative use cases.

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 provides explicit guidance: 'Use this to inspect or analyze the raw bytes of arbitrary data; use webdev_base64_image_encoder instead to turn an image into a Base64 data URI, or an encoding_decoding tool to convert between encodings.' This clearly states when to use the tool and when not, with specific alternatives.

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