Create from template and embedded sending

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

Discloses the creation and immediate link generation behavior, which aligns with annotations (readOnlyHint=false). It adds context beyond annotations but could mention potential side effects like link expiration.

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, no unnecessary words. Purpose and constraint are front-loaded.

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, an output schema, and high schema coverage, the description covers the core goal. Minor missing context about the 'type' parameter's effect, but schema fills that gap.

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 parameters are well-documented in the schema. The description does not add significant new information beyond what is in the schema.

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/group from a template/group and immediately creates an embedded sending link. The phrase 'ONLY for templates and template groups' distinguishes it from siblings like create_embedded_sending.

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 states the tool is only for templates and template groups, providing clear context. However, it does not explicitly contrast with alternatives like create_embedded_sending or create_from_template.

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