baseaddr.detect

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

With no annotations, the description carries full responsibility for disclosing behavior. It says only 'Run base-address detection' with no indication of side effects, mutability, required permissions, or what changes occur to the binary/database. This is a critical gap for a tool that likely modifies analysis state.

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?

The description is extremely short (4 words), which is concise but severely under-specified. It lacks necessary context for a tool with multiple parameters and a technical domain. Conciseness should not come at the expense of minimal usability.

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 tool has 8 parameters, no output schema, and no annotations, the description provides virtually no context. It does not explain what base-address detection does, how to interpret results, or how this tool relates to the broader baseaddr family. The description is completely inadequate for an agent to use this tool correctly.

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 schema has 8 parameters (session_id, analysis, alignment, arch_name, etc.) with zero description coverage in the schema itself. The tool description adds no meaning to any parameter—it does not mention parameters, their roles, or how they affect detection. The agent gets no help understanding what values to supply.

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 states 'Run base-address detection', which is a clear verb+resource combination. However, it does not differentiate the tool from siblings like baseaddr.reasons or baseaddr.abort beyond the action verb 'detect'. The purpose is vaguely clear but lacks specificity about what detection entails.

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 versus alternatives such as baseaddr.reasons or baseaddr.abort. There is no mention of prerequisites (e.g., whether analysis must be complete) or context that would help an agent decide to invoke it.

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