create_template

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

With no annotations, the description carries full burden; it discloses the creation behavior, required fields, tab structure, and default email subject behavior. It does not mention error handling, idempotency, or permission requirements, but the detail provided is substantial for a create 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?

The description is long but tightly organized with labeled args, bullet points, and a Returns line. Every sentence conveys meaningful detail for complex nested structures, and there is no fluff 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 tool's complexity (3 required params with nested structures, multiple content-source options, and signing-field rules), the description fully explains input semantics, defaults, and return values. It is complete enough for an agent to invoke the tool correctly without additional context.

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 description goes far beyond the bare-bones schema, explaining each parameter's sub-fields, content source alternatives (documentBase64/documentPath/documentUrl), tab rules, routing order semantics, and optional fields with defaults. This is essential because the schema has no per-property descriptions and 0% 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 opens with 'Create a new DocuSign template (documents + signer roles + signing fields)', which clearly identifies the verb (create), resource (DocuSign template), and scope. This distinguishes it from siblings like 'list_templates' and 'create_envelope_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 explicit guidance on when to leave name/email empty and fill later via create_envelope_from_template, naming the alternative tool. However, it does not broadly state when to use this over create_envelope_from_documents for one-off envelopes, so it stops short of full when/when-not coverage.

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