navigate_to

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

No annotations provided, so description must carry full burden. It only states the basic action of moving the cursor/view. Lacks disclosure of side effects (e.g., impact on current analysis context), error behavior for invalid addresses, or whether this modifies any state beyond the GUI view.

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?

Two concise sentences, front-loaded with the verb 'Jump'. No redundant information. However, it could be more informative while remaining concise, e.g., by specifying address format.

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?

For a simple tool with one parameter and an output schema, the description is minimally adequate but lacks crucial details about address format and error conditions. The output schema may cover return values, but the description still leaves gaps in usage context.

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%. The description does not explain the format expected for the 'address' parameter (e.g., hex, decimal, with or without 0x prefix). No added meaning beyond the raw schema field name 'Address'.

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 verb 'jump' and resource 'cursor'/'view', describing moving the GUI cursor to an address. This is distinct from sibling tools like disassemble or get_bytes, which analyze or retrieve data rather than navigate.

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 vs alternatives. Does not specify prerequisites, such as needing a valid address, or when to prefer other navigation tools like search_text or disassemble_range.

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