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

Annotations already declare read-only, open-world, and idempotent behavior. The description adds useful context beyond that: it needs SSH for mode: ssh, it verifies specific files, it re-detects every component, and it returns a missing list. It stops short of richer operational details such as failure handling, but output schema likely covers the return shape.

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 compact and front-loaded: purpose first, then read-only/SSH constraint, then usage guidance and alternatives. Every sentence carries distinct information and none is redundant.

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?

Given the tool's complexity, rich nested schema, annotations, and an output schema, the description supplies everything needed for correct selection and invocation. It covers purpose, prerequisites, automation context, sibling alternatives, and the key SSH caveat.

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 the schema already explains all six parameters, including the nested target fields. The description only moderately reinforces target and mode: ssh behavior, adding little meaning beyond what is already in the schema for dryRun, skipRepo, workspace, components, and profileUrl.

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 specific verb and resource: re-check a target after a clone, confirm two expected files exist, and re-detect components returning the missing list. It clearly distinguishes this from apply_clone and plan_clone by naming their roles.

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?

It explicitly says to use it after apply_clone, notes that bootstrap_host runs it automatically, and says to call verify_clone directly only for a targeted re-check. It also points to plan_clone for a pre-clone preview, covering when and when-not to use it.

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