edb_disassemble_range

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description doesn't need to repeat these. It adds behavioral context by stating the tool is for full function analysis, which implies larger ranges. No contradictions.

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?

Extremely concise: one sentence for purpose, one for differentiation, one for usage, then param list. Front-loaded and every sentence adds value without waste.

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?

Despite no output schema details in description, it states 'Returns: str: Disassembly listing'. Combined with annotations and clear parameter docs, it provides complete context for an AI agent to use this tool safely and effectively.

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 documents both parameters (start_address and end_address) with hex examples, adding meaning beyond the schema. Schema coverage is 0% per context, so description carries the full burden and does so well.

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 memory range from start to end address, with a specific verb and resource. It differentiates from the sibling edb_disassemble which uses instruction count, making the purpose unmistakable.

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?

Explicitly contrasts with edb_disassemble ('Unlike edb_disassemble...'), guiding the agent to use this tool for exact address ranges instead of instruction count. States it's useful for full function analysis, providing context.

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