loader.rebase

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

With no annotations, the description carries full burden to disclose behavioral traits like destructiveness, side effects on analysis, or required state. The description only states 'Rebase BinaryView' with no behavioral information whatsoever.

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?

At three words, the description is underspecified rather than concise. It fails to include necessary information while being short. Conciseness requires efficiency without sacrificing essential details; this sacrifices everything.

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?

Given the complexity of a rebase operation (likely affecting analysis state, address formats, and interaction with other tools) and the absence of any annotations or output schema, the description is completely inadequate. It provides no context for safe or effective use.

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%, meaning the input schema provides no parameter descriptions. The tool description does not explain any of the three parameters (force, address, session_id). It adds no value beyond the raw schema, leaving the agent with no guidance on parameter semantics.

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 'Rebase BinaryView' states a verb+resource but is extremely terse. It does not distinguish this tool from sibling loader tools like 'loader.load_settings_set' or base address tools like 'baseaddr.detect'. The purpose is clear in a minimal sense but lacks specificity to differentiate.

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 is provided on when to use this tool vs alternatives. There is no mention of prerequisites, context (e.g., after base address detection), or when rebasing is appropriate. The description is entirely absent of usage direction.

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