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

The annotations already indicate this is not read-only (readOnlyHint=false) and is destructive (destructiveHint=true). The description adds useful behavioral context: the tool validates the workflow before saving, and cannot publish or activate. This goes beyond the structured annotations, though it does not detail side effects like overwriting existing drafts.

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 two sentences: the first states the core action, the second clarifies a key limitation. Every word is relevant, and it is optimally front-loaded with the purpose. No fluff or repetition.

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?

The tool is relatively simple (one parameter, no output schema), but the nested 'workflow' object is unspecified, and the description does not indicate what a valid workflow declaration looks like or what the tool returns. The description covers the main purpose and limitation, but for a validation-saving tool, more detail about the input structure would be expected for full completeness.

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?

The schema has one parameter 'workflow' with no description and additionalProperties true, so schema coverage is 0%. The description refers to it as a 'workflow declaration,' giving a minimal hint, but does not explain what fields or structure are expected. The description fails to compensate for the lack of schema documentation, leaving the parameter semantics largely unexplained.

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 clearly states the tool's purpose: 'Validate and save a workflow declaration as a draft.' The verb 'save' is specific, the resource is a 'workflow draft,' and it is distinguished from publishing or activation by explicitly saying it cannot do those. This differentiates it from other save tools like save_intake_draft.

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 gives clear context: this tool is for saving drafts and explicitly excludes publishing or activating. This helps the agent know when not to use it (when the goal is to publish). However, it does not name an alternative tool for publishing, so it receives a 4 rather than a 5.

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