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

With only a title annotation, the description carries the full burden and does so: atomicity, replacement of prior installs, built-in override, sha256 verification with all-or-nothing failure, required flow.json/steps shape, and a privilege-escalation warning about third-party eval_steps running with engine privileges in session pages. This is exceptional disclosure for a mutation tool.

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?

Front-loaded with the action and destination, then layers verification, atomicity, and the security caveat in order of importance. It is dense and long-sentenced but nearly every clause carries operational information; only the built-in override detail is arguably extraneous.

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?

No output schema exists, and the description compensates by enumerating the receipt contents (files, total bytes, step count, eval_steps). Combined with failure semantics and the env-configured source, an agent has everything needed to invoke and interpret 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?

Schema coverage is 100% and the single `name` param is already well documented there, so the baseline is 3. The description adds genuinely non-schema meaning: the source remote is env-configured via AGINXBROWSER_DUPHUB_URL and is never a parameter, which prevents an agent from trying to pass a URL.

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?

States a specific verb (install) and resource (third-party flow from DupHub) plus the concrete landing location and the effect of making it runnable by name via flow_run. The distinction from the sibling flow_run is made explicit, so an agent can tell the two apart without opening a schema.

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?

Positively routes to flow_run for execution and implicitly frames this as the prerequisite setup step, and the security note ('review before running') gives a when-to-be-careful cue. It stops short of stating explicit exclusions or prerequisites (auth, network access) for the install itself.

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