docusign_create_envelope

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

Annotations already provide readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful behavioral context: governed routing, idempotency key semantics, that 'effect' is verified by Spring, and that approval_ref is needed when resuming a write. No annotation contradiction is present.

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 compact and well-structured with a clear Args list. The opening line is somewhat redundant with the tool name, but overall every line earns its place and the format is easy to parse.

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?

For a Docusign envelope creation tool, the domain-specific payload is hidden inside `arguments` and is completely unspecified. An agent receives no examples, field names, or indication of required envelope properties, making correct invocation doubtful. The output schema may cover return values but does nothing to compensate for the missing input semantics.

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 description coverage is 0%, so the description must carry the burden. It gives one-line glosses for every parameter, but the critical `arguments` parameter is described only as 'JSON string of arguments for the connector operation,' which is almost tautological and gives no indication of the actual Docusign envelope payload needed.

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 identifies the tool as the Docusign connector operation `create_envelope` with its platform tool name, clearly indicating the verb (create) and resource (envelope). However, it does not explain what 'creating an envelope' means in Docusign terms, nor does it differentiate itself from the sibling docusign_observe_envelope_status beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives. The routing/governance statement is a constraint, not a usage guideline, and the sibling docusign_observe_envelope_status is never referenced.

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