Create a full replication kit

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

The description discloses meaningful behavior beyond annotations: it writes to a local folder, loads the page once, and generates a defined set of output files. This complements annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) with no contradiction.

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?

Two sentences, no fluff. It leads with the core purpose, enumerates outputs in a scannable colon list, and ends with a performance benefit. Every clause earns its place.

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?

The tool is complex (18 parameters, many outputs), but the schema and output schema handle detailed specifications. The description adds the essential context of aggregation and speed advantage. A brief caveat about potential heaviness or overwrite behavior could push it higher, but current coverage is solid.

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 input schema covers all 18 parameters with detailed descriptions, so the baseline is 3. The prose description doesn't add parameter-level details, but it doesn't need to because the schema is exhaustive.

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 uses a specific verb ('capture') and resource ('everything needed to replicate a website') and clearly lists the deliverables. It distinguishes itself from siblings by emphasizing it captures everything in one shot and is faster than calling individual tools separately.

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 states the advantage over calling individual tools separately ('Loads the page once, so it is much faster'), giving clear guidance on when to prefer this tool. However, it doesn't explicitly mention when not to use it or edge cases where individual tools might be preferred.

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