edb_jump_to_address

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

Disclosures include setting instruction pointer and equivalence to a UI action. Adds context beyond annotations (destructiveHint) by explaining the effect. Could clarify if execution resumes after jump.

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?

Three sentences plus Args/Returns, front-loaded with core purpose. Every sentence adds value, no redundancy.

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?

Single parameter with clear description, simple return type. Output schema present. Description covers purpose, usage, parameter details, and return. Fully complete for this tool.

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?

Parameter description in schema already provides examples. Description repeats 'Target' and examples, adding minimal value over schema. Baseline 3 is appropriate given schema coverage is effectively 100%.

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?

Clearly states the tool jumps to a specific address and sets the instruction pointer. It provides equivalent UI action and distinguishes from stepping/continuing siblings via 'skip code or continue from a specific location'.

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 states use cases: 'skip code or continue from a specific location'. Does not explicitly describe when not to use or name alternatives, but the context is clear given sibling tools like edb_step_instruction.

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