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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: the copy is server-side and 'content never passes through your context,' the read permission requirement ('any doc the user can read'), and the ~1s cost. It stops short of stating what happens on a name collision or whether an existing destination doc is overwritten.

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?

Three dense, front-loaded sentences with no filler; the purpose, workflow position and performance comparison each earn their place. The closing speed comparison slightly overlaps the 'THE fast path' claim but is what makes the alternative concrete.

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?

Covers purpose, permission scope, cost, and the follow-up tool to use, which is nearly everything needed to invoke it correctly. With no output schema, however, it does not say what the copy returns (new doc name/slug/URL), which the agent would need to chain into patch_doc.

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 slug, account, doc_name and new_name are already documented in the schema. The description only reinforces 'under a new name' and the farm destination, adding no format or disambiguation detail (e.g. slug vs doc_name precedence) beyond structured data. Baseline 3 is correct here.

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 precise verb+resource+scope: 'Server-side copy of any HTML doc the user can read (their own OR shared with them) into their own farm under a new name.' It immediately distinguishes itself from the get_doc_html/host_html_content path named in the same sentence, so an agent can tell it apart from siblings without opening the 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?

Explicitly names the workflow it belongs to ('THE fast path for building a modified version of an existing doc... then use patch_doc for the differences') and names the alternative it beats ('Vastly faster than get_doc_html + re-hosting'). The condition selecting this tool over the alternative is spelled out.

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