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

Annotations already indicate a mutating, non-destructive operation. The description adds useful behavioral context by explaining that the operation branches a draft rather than altering the base, copies agent/queue/trigger bindings, and defaults to the active revision. It does not cover permissions or return values, but the core behavior is transparent.

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 a single concise sentence with no filler. The most important behavior—draft creation, branching, default source, and copied bindings—is clearly front-loaded.

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 low-complexity create-style tool with no output schema, the description adequately covers core behavior, defaults, and copied resources. It omits return-value details and any mention of later activation, but those are minor and inferable from the draft-revision semantics.

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%, with all four parameters already documented, including the base_revision_id default. The description reinforces branch/copy semantics but does not add per-parameter meaning beyond what the schema already provides.

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 and resource: 'Create a draft revision branched from a base revision.' It also names the distinct automation context by mentioning copied agent, queue, and trigger bindings, which distinguishes it from generic createRevision/createSkillRevision.

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 description makes the usage context clear: the tool creates a draft revision, defaults to the active revision, and branches from a base revision. However, it does not explicitly state when to prefer this over related tools such as createRevision, activateAutomationRevision, or promoteRevision, nor does it mention exclusions.

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