save_thermomix_recipe

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

No annotations are provided, so the description bears full responsibility. It mentions the output format and target folder but lacks details on overwrite behavior, error handling, or prerequisites. The basic file-saving operation is described, but depth is limited.

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 concise, using two sentences to convey the core purpose and parameter details. It front-loads the main action. However, it could be slightly more structured or include a brief note on behavior.

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?

Given the tool's low complexity (2 parameters) and presence of an output schema, the description covers essential aspects: purpose, parameters (meaning), and target folder. It lacks alternative tool guidance but is otherwise adequate for a simple save operation.

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?

With 0% schema description coverage, the description effectively compensates by explaining what `markdown` contains (full card with YAML frontmatter) and that `filename` is optional, derived from the heading. It adds meaningful context beyond bare parameter names.

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 specifies the tool's action: saving a finished recipe card as a Markdown file. It distinguishes from siblings (fetch, find, upload) by focusing on local file saving.

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 explains how to use the parameters but does not provide explicit guidance on when to use this tool versus alternatives like upload_thermomix_recipe. Usage context is implied but not elaborated.

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