disassemble_at_address

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

No annotations are provided, so the description carries the full burden. It explains what the tool does and lists parameters, but lacks details on side effects, permissions, error conditions, or output format beyond a generic 'Disassembly output'. The description is adequate but not rich.

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 a concise docstring with Args and Returns sections. Purpose is front-loaded ('Disassemble code...'). Every sentence adds value, no fluff, well-organized.

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 5 parameters and an existing output schema, the description covers all inputs and mentions return type. It does not detail error handling or file format expectations, but for a straightforward disassembly tool, it is sufficiently complete. An output schema exists, so return details are not mandatory in the description.

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 0%, so the description must explain parameters. It does so clearly: file_path as absolute path, virtual_address as hex string, size with default, arch auto-detected, max_instructions default. Adds context beyond the schema (e.g., 'Auto-detected if omitted' for arch).

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 that the tool disassembles code at a specific virtual address in a binary file. The verb 'Disassemble' and resource 'code at a specific virtual address' are specific and distinguish from sibling tools like disassemble_entrypoint or disassemble_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 does not provide any guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or when not to use it. Sibling tools exist for different addressing modes (e.g., entrypoint, raw offset), but this is not addressed.

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