disassemble_hex

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

With no annotations, the description must convey all behavioral traits. It states the tool disassembles hex into assembly and returns formatted output. It does not disclose side effects, if any, but for a disassembly tool this is acceptable. However, it could mention that the operation is non-destructive.

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 well-structured with Args and Returns sections, making it easy to parse. It is slightly verbose but every sentence adds value. The main purpose is front-loaded.

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 that an output schema exists (as per context signals), the description adequately explains the return format. All aspects of the tool are covered, including input formats, default values, and usage hints. It is complete for a disassembly tool.

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?

The description adds substantial meaning beyond the input schema: for hex_code it provides examples and notes spaces are auto-stripped; for arch it directs to list_supported_architectures; for base_address it gives a format example; for max_instructions it explains the 0 meaning. This compensates for the 0% schema description coverage.

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 verb 'disassemble' and the resource 'hex-encoded byte string', with immediate clarification of input format. It distinguishes itself from sibling disassembly tools that operate on different inputs (e.g., at a memory address, entrypoint, or file section).

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 context on when to use this tool by specifying it handles hex-encoded byte strings and defaults to x86_64 architecture. However, it does not explicitly mention alternatives or when not to use it, leaving the agent to infer from the sibling tool list.

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