disassemble_function

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

No annotations are provided, so the description carries full behavioral burden. It conveys only that the entire function is disassembled, but says nothing about output format, required session state, effects, or rate limits. The '(pdf)' token is undefined and adds no reliable behavioral context.

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?

A single, short, front-loaded phrase. It is economical, though the cryptic '(pdf)' suffix wastes a few words that could have been used for a clarifying clause.

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?

With no annotations, an output schema present (so return format is covered), but 0% parameter documentation and no usage context, the description is incomplete for an agent to call this correctly. It does not explain the required session context or address semantics, nor when to prefer it over 'disassemble' or 'analyze_function'.

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% for two parameters ('address', 'session_id'), both with null defaults and no descriptions. The tool description offers no explanation of what 'address' should be (entry address? any address inside the function?) or how 'session_id' is used, so it fails to compensate for the schema gap.

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?

Clear verb+resource: 'Disassemble' + 'function'. The parenthetical '(pdf)' is cryptic and unexplained, likely a typo or plugin-specific term, which slightly muddies an otherwise clear purpose. It is distinguishable from siblings like 'disassemble' (possibly raw address disassembly) and 'analyze_function' (higher-level analysis).

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?

No guidance on when to use this versus sibling tools such as 'disassemble' or 'analyze_function'. The agent is left to infer the distinction from names alone, which is risky given the overlapping address-based disassembly tools.

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