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

Annotations already declare idempotentHint and destructiveHint, so the 'Idempotent' claim is partly redundant, but the description adds genuinely new behavior: the consent gate ('without confirm:true it returns the plan'), which explains the dry-run semantics an agent must know before mutating a host. It does not cover credential/permission requirements or SSH auth failure modes, which list_required_credentials and run_auth_flow imply are relevant.

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?

A dense but well-ordered paragraph: what it does, the consent/idempotency contract, then routing to siblings. Every clause carries information, though the idempotent/consent sentence and the routing sentence could be split for faster scanning.

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?

With an output schema present, return values need no explanation, and the description covers scope, consent behavior, and sibling routing adequately for a 4-param install tool. The main remaining gap is prerequisites — which credentials the target needs and when to call list_required_credentials first.

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 100%, so target/mode/confirm/component are already documented in the schema. The description restates that component must come from get_workbench_info and repeats the confirm plan behavior rather than adding format or constraint detail (e.g. workspace/profile repo semantics). Baseline 3 applies.

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) plus resource (a single Workbench component) with concrete id examples, and explicitly distinguishes itself from apply_clone (subset) and bootstrap_host (first-time provision). An agent can select it without opening any sibling 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?

Gives explicit routing rules: 'Use it for one targeted component; use apply_clone for a component subset, or bootstrap_host for a first-time end-to-end provision', plus an anti-pattern warning ('do not combine them for the same host and change'). This is textbook when-to-use guidance.

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