Api managed documents create new draft create

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is covered. The description adds meaningful behavior – the new draft is cloned from the current revision – but does not say what happens to the existing revision, whether the draft is editable, or what permissions/state preconditions apply, so it is useful but thin.

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 single sentence with no filler, and the core action plus cloning semantics are front-loaded so an agent can grasp the tool at a glance.

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 single-parameter mutation tool with no output schema, the description covers the essential action, but it omits any explanation of the id parameter and does not describe what the draft result looks like or any preconditions, leaving gaps an agent would have to probe.

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?

There is one required string parameter 'id' with 0% schema description coverage, and the description never mentions it. It only implicitly suggests the id identifies the managed document whose current revision is cloned; it does not state whether it is the document id, revision id, or ref, leaving a real ambiguity.

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 ('Create a new draft revision') plus the key mechanism ('cloned from the current revision'), which lets an agent distinguish this from plain managed-document creation. It does not name any sibling tool explicitly, keeping it just short of a 5.

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?

The cloning behavior implies the intended context (starting a new revision on an existing managed document), but there is no explicit when-to-use/when-not guidance and no reference to alternatives such as the generic managed_documents_create or document_revisions_create endpoints.

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