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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, and the description does not contradict them. However, it adds no behavioral context beyond those hints — nothing about what a save overwrites, hash guarding, or concurrency — so it contributes no value over the structured metadata.

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?

It is a single short sentence with no wasted words, but this length reflects under-specification rather than conciseness. There is nothing front-loaded to help an agent decide or act.

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 10-parameter destructive mutation tool with no output schema, the description omits required inputs, the meaning of optional fields, and the version/hash semantics that govern whether it POSTs or PATCHes. An agent cannot safely invoke this from the description alone.

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 are 10 parameters and schema description coverage is only 10%, so the description carries the burden of explaining parameters and instead says nothing about any of them (nodes, edges, failure_policy, expected_definition_hash, result_projection, version_id). None of the ambiguous or untyped fields are clarified, leaving the caller to guess.

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 'Save the automation's draft' essentially restates the name and title (mcp_recipe_save_draft / Save Automation Draft) without adding scope, target, or effect. It does not distinguish itself from close siblings like mcp_recipe_open, mcp_recipe_copy, or mcp_recipe_preflight beyond the generic word 'save'.

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?

No when-to-use guidance is given: it doesn't say when a draft should be saved versus using recipe_preflight, recipe_open, or recipe_history, nor mention prerequisites such as an open board. The one useful routing hint (new draft vs existing version) lives in the schema, not the description.

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