Create Template

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

The description discloses that the operation is blocked in read-only mode, which is a behavioral trait beyond annotations' readOnlyHint:false. It also specifies the validation requirement for html_body/text_body, adding useful operational context. No contradiction with annotations; readOnlyHint:false aligns with a write operation.

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?

Two short sentences with purpose first, no filler. The first sentence states the action, the second gives a key constraint. Every word earns its place.

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 7 parameters and low schema coverage, the description leaves significant gaps: it doesn't clarify template_type vs layout_template relationship, the subject requirement for Standard templates, or alias uniqueness. The presence of an output schema does not compensate for missing parameter semantics and conditional rules.

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 only 43%, so the description must compensate. It adds the critical rule 'Provide at least one of html_body or text_body' and mentions 'template or layout' hinting at template_type, but does not explain html_body, text_body, layout_template, or the conditional subject requirement for Standard templates. Partial compensation but incomplete.

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 uses a specific verb 'Create' with the resource 'template or layout', clearly distinguishing it from sibling tools like edit_template, delete_template, or send_email_with_template. It also states a key requirement (at least one body) that clarifies the action further.

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?

It explicitly mentions the tool is blocked in read-only mode and requires at least one of html_body or text_body, giving clear operational context. However, it does not explicitly contrast with alternatives like edit_template or validate_template, only implying when to use via the word 'new'.

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