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

The description clarifies that the operation creates a new owned draft revision rather than modifying the frozen one, which aligns with and slightly extends the annotations (readOnlyHint=false, destructiveHint=false). It does not disclose side effects, whether the source revision is preserved, or what the new revision's status will be beyond 'draft'.

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, well-structured sentence that front-loads the core action and source state. It is concise with no filler, though it could have included more operational context without becoming bloated.

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?

With 7 parameters, no output schema, and no parameter guidance, a one-sentence description is insufficient for an agent to invoke this tool confidently. It lacks information about required fields beyond asset_id, how the revision relates to the asset, what happens upon creation, and what response to expect.

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 only 14%, and the description provides no parameter-level guidance. It does not explain the meaning of title, channel, content, asset_type, scheduled_for, or revision_notes, nor does it clarify that asset_id must be a full UUID beyond what the schema already states.

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 names a specific verb ('create'), a specific resource ('owned draft revision'), and a clear source state ('frozen submitted/approved/rejected revision'). This meaningfully distinguishes it from sibling tools like create_content_asset or update_content_asset, though it does not explicitly name those alternatives.

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 phrase 'from a frozen submitted/approved/rejected revision' implies the tool is used when an existing revision is in a terminal state and a new draft branch is needed. However, it does not explicitly state when not to use it or mention alternative tools such as update_content_asset, leaving the usage context somewhat implicit.

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