Create from template and embedded invite

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

Annotations already indicate mutation (readOnlyHint=false). The description adds that the operation happens 'immediately' and applies only to templates, which is useful. However, it does not disclose side effects, auth requirements, error scenarios, or other behavioral traits beyond what annotations provide.

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 concise sentences, front-loaded with the core action. Every sentence adds value without unnecessary words.

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 an output schema present, return values don't need explanation. However, given the complexity and multiple sibling tools, the description could be more complete by explaining when to use this tool versus similar ones (e.g., create_embedded_invite). It is adequate but not comprehensive.

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 description adds no additional parameter meaning beyond what the schema already provides. The restriction to templates is already encoded in the entity_type enum.

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 states it creates a document from a template and then creates an embedded invite. It specifies 'ONLY for templates and template groups,' which distinguishes it from generic invite tools. However, it could be more explicit in contrasting with sibling tools like create_embedded_sending_from_template.

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 does not provide explicit when-to-use versus alternatives. It notes the tool is only for templates, but it lacks guidance on when to prefer this over similar tools (e.g., create_embedded_invite, create_from_template). No prerequisites or usage context are mentioned.

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