Create from template and send invite

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

The description openly discloses that the tool sends an invite immediately after creating the document, aligning with the annotations (readOnlyHint=false). It does not contradict annotations, and provides useful behavioral insight beyond what annotations convey.

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 extremely concise with only two sentences. The first sentence covers the entire action, and the second adds a critical restriction. No unnecessary words or repetition.

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?

Given the presence of an output schema (context says has output schema: true) and 100% schema description coverage, the description adequately covers the main action and scope. It could mention prerequisites or error conditions (e.g., template must exist) for full completeness, but it is sufficient for an agent.

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 schema provides 100% description coverage for all 4 parameters, so the baseline is 3. The description adds value by reinforcing that the tool works only with templates/template groups, which helps clarify the entity_type parameter. However, it does not add new parameter-specific details.

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 that it creates a document or document group from a template/template group and immediately sends a signing invite. It explicitly distinguishes itself by noting that it is ONLY for templates and template groups, which differentiates it from sibling tools like send_invite or create_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 provides strong guidance by stating the tool is only for templates and template groups, implying when to use it. However, it does not explicitly mention alternatives for non-template documents, which would improve clarity further.

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