install_tools

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates state and reaches the network; the description's 'download' corroborates but adds nothing beyond that. It does not say where files land, whether existing installs are overwritten, how long a download takes, or how 'dual operator consent' is actually enforced — the one distinctive claim is left opaque.

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?

It is short with no filler, but it is an under-specified fragment rather than a front-loaded sentence. Length is not the problem; the missing content is.

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?

For a non-read-only, open-world tool with a required consent flag and no output schema, the definition should say what gets installed, from where, and what the confirmation gates. None of that is present, so an agent cannot confidently decide whether or how to call 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?

The single required boolean confirm_downloads has 0% schema description coverage, so the description must carry it — but it never mentions the parameter or explains whether setting it to true constitutes the 'dual operator consent' or merely part of it. That ambiguity matters for a state-changing tool.

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 phrase 'Download official engines only with dual operator consent' is a fragment that names an action (download) but not the resource clearly — 'engines' is undefined, and the tool name (install_tools) implies installation, not just download. It gives no hint of what distinguishes this from siblings like capabilities, doctor, or list_artifacts.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. 'Only with dual operator consent' gestures at a precondition but never explains what qualifies, who the two operators are, or what to do if consent is absent.

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