re_install

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

No annotations are provided, so the description must disclose behavioral consequences. It only says 'Download' but does not mention whether existing installations are overwritten, network requirements, side effects on the filesystem, or that omitting 'tool' lists available options. This lack of detail undercuts transparency for a mutating operation.

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 a single, front-loaded sentence that immediately conveys the tool's core function. It wastes no words and avoids redundant restatement of the tool name.

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?

This tool has no annotations or output schema, so the description must carry the full load. It fails to explain return values, error behavior, side effects, or the 'omit to list' behavior implied by the schema. For a tool that installs software, critical operational details are missing.

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 only 33% (only 'tool' has a description). The description adds value by enumerating valid values for 'tool' (rizin/x64dbg/ghidra/cutter/capstone/pefile), but it does not explain the semantics of 'force' or 'refresh_url'. With such low coverage, the description should compensate but fails to address two of three parameters.

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 action (Download open-source RE kits) and the specific targets (native/re_tools and pip packages), distinguishing it from sibling tools like re_rizin or re_status. The verb 'Download' and resource list make the tool's purpose unambiguous.

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?

The description implies clear usage: when you need to install these specific RE kits. However, it does not explicitly state when not to use it or contrast with alternatives like re_rizin or re_deploy. The context is clear enough for basic selection but lacks explicit exclusions.

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