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

The description adds meaningful behavioral detail beyond the annotations by stating 'This stores conversion settings only; converted bytes are generated on download.' This clarifies the key side effect: no converted bytes are produced at save time. The annotations declare readOnlyHint=false, which is consistent with saving, and there is no contradiction.

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, front-loaded with the core purpose and followed by the crucial behavioral qualifier. Every sentence earns its place, and there is no redundant or vague filler.

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 a complete input schema, annotations, and an output schema present, the description covers the essential purpose and behavior. It does not explain edge cases like overwriting an existing recipe of the same name, but for a moderate-complexity recipe-save tool, the description is sufficiently complete for correct invocation.

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 coverage is 100%, with all five parameters described in the schema. The description correctly summarizes them as 'conversion settings only' but adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Save a reusable image download format recipe for an image file.' The clarifying phrase 'converted bytes are generated on download' distinguishes this from a sibling like transform_image, which likely performs conversion immediately. This gives an agent a clear idea of what the tool is for.

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 'reusable' and 'generated on download' imply this is for defining persistent conversion presets rather than performing immediate conversions, but the description never explicitly says when to use this versus transform_image or upload_file. Alternatives are not named, and no exclusion conditions are provided.

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