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

Annotations already flag openWorldHint=true and destructiveHint=true; the description goes further by naming the exact files written and that they are 'overwriting any existing versions in place' (matching destructiveHint), plus the open-world behaviors: network requests to the target site, sitemap reads, and same-origin link following, and the cached-dataset/refresh behavior. Nothing contradicts the annotations.

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-loads the core action and artifacts before the constraints, and each sentence carries information (outputs, write semantics, open-world behavior, routing, parameter relationships). It is dense but not padded, with only mild redundancy in the trailing parameter summary.

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 9-parameter, destructive, open-world tool with an output schema, the description covers what an agent needs: writes and overwrites, network access, cache bypass, local-vs-hosted parameter applicability is handled in schema, and parameter relationships are summarized. Return values are covered by the output schema.

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 baseline would be 3; however the description adds genuine meaning by clarifying that 'description is the target domain and statement is the desired outcome (both optional)' — the schema only says 'Freeform description input' for description, so this is real added value — and that refresh=true bypasses a cached dataset.

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 concrete verb and resource ('Crawl and capture a target domain into a clone dataset + manifest') and names the artifacts produced (vdd/clone-dataset.json, vdd/clone-manifest.json, vdd/clone.md). It explicitly distinguishes itself from the vdd_* siblings by declaring it is not part of the VDD phase pipeline.

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 both positive and negative routing: 'Use for cloning an external site; it is not part of the VDD phase pipeline, so for the normal init→validate flow call those phase tools instead.' The alternative (phase tools) and the condition selecting it are stated outright.

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