disassemble

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

With no annotations, the description carries the full burden. It states it produces disassembly output using objdump, implying a read-only operation. However, it does not explicitly confirm non-destructiveness, required permissions, or potential side effects. The disclosure is adequate but not comprehensive.

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, front-loading the purpose. It is concise without unnecessary words. A slight improvement could be more explicit separation of the fallback logic.

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 output schema exists (though details not provided), the description's brief return statement may suffice. However, there are many sibling tools, and the description does not explain how this tool differs from 'get_disassembly' or 'analyze_elf'. It lacks completeness for an agent to choose correctly among similar options.

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 0%, so the description must compensate. It describes each parameter: symbol (function name), address (hex), lines (max count, default 50). It also adds fallback logic: address used if symbol is empty. This goes beyond the schema's bare definitions.

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 disassembles a function or address range from the project ELF file, using objdump. This gives a specific verb and resource, but it does not distinguish it from the sibling 'get_disassembly' which likely performs a similar function.

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?

It mentions 'Uses the configured objdump tool', providing context on how disassembly is performed. However, it offers no guidance on when to use this tool versus alternatives like 'get_disassembly' or under what conditions it is appropriate. No exclusions or when-not-to-use instructions are given.

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