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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the key destructive behavior: 'overwrite: If true, replace existing recipe with same name.' It also explains the file format. It stops short of describing what happens if the recipe already exists and overwrite is false, or whether content is validated.

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 well-organized with a clear action sentence, a template block, and an Args list. It is longer than necessary because the markdown template repeats some prose, but all content earns its place by defining the exact expected format.

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 description is largely complete for a creation tool: it identifies the parameters, the required format, and the overwrite behavior. An output schema exists, so return-value details are not required. It lacks only explicit failure semantics when name conflicts occur without overwrite.

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 0%, so the description must fully compensate. It does: name is described with a snake_case example, content is described as full markdown and illustrated with a detailed template, and overwrite's effect is explicitly stated. This is strong semantic coverage for every parameter.

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 begins with a specific verb and resource: 'Create a new workflow recipe.' It also clarifies the resource type (markdown files with numbered steps), and the create action clearly distinguishes it from sibling tools like get_recipe, list_recipes, and delete_recipe.

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 intended use is clearly implied: call this tool to create a workflow recipe. However, it does not explicitly discuss when not to use it, nor does it contrast with alternatives such as get_recipe for reading existing recipes or delete_recipe for removing them.

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