Verify like a new user

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

Annotations already cover the safety profile (openWorldHint=true, destructiveHint=false), and the description adds real behavioral context: execution happens in an isolated brand-new temp folder, installs come from the real registry, git clone is an alternative path, and installed executables land on PATH. It omits cleanup behavior, timeouts, and how failures are surfaced.

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 sentences with the core scenario front-loaded and no filler. The PATH note is a useful trailing detail rather than padding, though a bit more structure around outcomes could be added without bloat.

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 is a complex tool that installs packages and executes arbitrary commands over the network, with no output schema and minimal annotations. The description covers the setup scenario but says nothing about return values, error reporting, timeouts, or cleanup, leaving meaningful gaps for an agent invoking it.

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 60% (command, repoUrl, registry documented; name and version are not). The description loosely maps to registry and repoUrl ('from the real registry (or git clone the repo)') but adds no syntax, format, or defaults for the undocumented name/version parameters, so it only partially compensates.

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 a concrete verb+resource: install the published package into a fresh temp folder and run a command, framed as a new-user verification. The 'brand-new temp folder' isolation makes the clean-room intent clear, though it never explicitly contrasts itself with siblings like install_tool or preflight.

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?

Usage is implied by the scenario ('verify like a new user', 'such as the README quick start'), giving the agent a concrete example of the intended command. However, there is no explicit when-to-use vs. when-not guidance and no mention of alternatives such as install_tool or preflight.

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