disassemble

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 does not state that this is a non-destructive read operation, whether it requires an active/selected session, or any constraints on address/count. 'session_id: Session to use' implies session dependence but does not explain it.

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?

Front-loaded with the verb and a compact arg list; no wasted sentences. The formatting is slightly mechanical but efficient.

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?

An output schema exists, so return values need not be explained. But for a disassembler with no annotations, the description omits behavioral context (read-only nature, session requirements, error conditions), leaving meaningful gaps.

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 compensate, and it lists all three parameters. 'address: Starting address or symbol' adds real meaning beyond the anyOf string schema, and count/session_id are explained, though tersely.

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?

States a specific verb ('Disassemble') and resource ('N instructions') with a command alias '(pd)'. However, it does not distinguish itself from the sibling 'disassemble_function', leaving ambiguity about when to use one over the other.

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 tool versus alternatives. With a sibling named 'disassemble_function' that presumably disassembles a whole function, the agent gets no help choosing between them or understanding prerequisites (e.g., whether an active session is required).

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