Create Template

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: the HTML is sanitized and an unsubscribe link is injected automatically, which tells the agent the stored result differs from input. No contradiction with 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 short sentences, zero filler. The core action is front-loaded and the sanitization/unsubscribe behavior and the alternative-tool routing each earn their sentence.

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?

For a two-parameter creation tool with annotations covering the safety profile and no output schema, the description covers action, side effects, and the alternative route. Only minor gaps remain, such as whether the created template returns an id.

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 only 50% (name has no description), but both parameters are simple and self-evident, and the description confirms the html parameter is the email body source. It adds the sanitization note but no format/size detail beyond the schema's 'Full email body HTML.'

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 a specific verb and resource ('Create an email template') plus the input modality ('from HTML'). It also names the sibling it is not (copy-gallery-template), so an agent can distinguish it from the other template tools without opening schemas.

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?

Explicitly routes the agent to copy-gallery-template for the alternative path ('To start from a professionally designed layout instead'), making the selection condition between the two tools unambiguous.

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