docuseal-mcp-server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that emails can be disabled via 'send_email', hinting at notification behavior, but fails to cover critical aspects such as authentication requirements, rate limits, error handling, or what happens upon creation (e.g., whether it triggers workflows). For a mutation tool with zero annotation coverage, this is a significant gap.

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 efficiently structured in a single sentence, front-loaded with the core purpose and followed by a clear breakdown of required and optional parameters. Every word earns its place, with no redundant information, making it easy to parse quickly.

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 complexity of a mutation tool with 4 parameters, no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks details on behavioral traits (e.g., side effects, permissions) and return values, which are crucial for safe and effective use by an AI 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?

Schema description coverage is 75%, with the 'message' parameter lacking a description in the schema. The description compensates by listing all parameters (template_id, signers, message, send_email) and clarifying their roles (e.g., 'message' as optional text for emails). It adds value beyond the schema by summarizing required vs. optional parameters, though it doesn't detail nested structures like 'signers' objects.

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 signature request') and resource ('from a template'), with specific required elements (template_id and signers). It distinguishes itself from sibling tools like 'create_template_from_pdf' by focusing on submissions rather than templates, though it doesn't explicitly contrast with other submission-related tools like 'list_submissions'.

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 implies usage by specifying required parameters (template_id and signers), suggesting this tool is for initiating signature requests from existing templates. However, it lacks explicit guidance on when to use this versus alternatives like 'create_template_from_pdf' for template creation or 'list_submissions' for viewing submissions, leaving some ambiguity.

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