Create from template and embedded invite

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

Annotations already indicate non-readOnly and non-idempotent behavior. The description adds that the tool creates both a document/group and an invite, but does not disclose other behavioral traits such as required permissions, error conditions, or side effects beyond creation. This is adequate given the annotation context.

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 consists of two sentences, no redundancy, and immediately conveys the core functionality and restriction. 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 a complex multi-step operation (create from template + embedded invite) and the presence of sibling tools for individual steps, the description clearly defines the scope. An output schema exists (not shown but indicated), so return value explanation is unnecessary.

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?

The input schema has 100% description coverage for all parameters, so the schema already provides meaning. The description does not add further parameter-specific guidance, meeting the baseline for high coverage.

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 the action ('Create a document or document group from a template or template group, then create an embedded signing invite immediately') and explicitly restricts usage to templates and template groups, distinguishing it from sibling tools that operate on documents or invites separately.

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 explicitly states the tool is ONLY for templates and template groups, providing clear context. However, it does not explicitly mention when to use separate sibling tools (e.g., create_from_template + create_embedded_invite) instead of this combined tool, but the presence of sibling names implies the distinction.

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