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

Annotations already flag mutation and non-idempotence, but the description adds valuable context: it changes stored data, repeating can create another template, it does not generate an image, and user confirmation should precede invocation. This goes well beyond the structured annotations.

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?

Three sentences front-load the core action and then add high-value caveats about non-idempotence, image generation, and user confirmation. There is no filler or repetition of schema details.

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 full schema coverage, an output schema, and informative annotations, the description supplies the missing context: repeat behavior, no image output, and confirmation requirements. Everything needed to invoke this tool correctly is covered.

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%, so the parameters are already fully documented with types, defaults, enums, and patterns. The description only adds that project, name, formats, and sizes should be user-confirmed, which is a usage caveat rather than new parameter semantics.

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?

States the specific verb 'Create' and resource 'Imagelato resizing and reformatting preset,' making it clear this is a template-creation operation. The phrase 'does not generate an image' and 'in an accessible project' further distinguish it from related operations.

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?

Implies use when the user wants a new template preset and instructs confirming project, name, formats, and sizes before invoking. However, it does not explicitly name alternatives like update_template or describe when not to use this tool.

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