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

No annotations provided, so description bears full burden. It mentions the action but does not disclose side effects, required permissions, response behavior, or behavior when the envelope is already signed. 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?

Single sentence, front-loaded with verb, no filler. Efficient for a simple tool.

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 simple schema but no output schema/annotations, description is too minimal. It lacks response details, error conditions, and prerequisites beyond the unsigned state. However, the tool's simplicity partially offsets this.

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 has one required param (envelopeId) with zero description coverage. The description adds the semantic constraint that the envelope must be unsigned, but doesn't explain how to obtain envelopeId or its format.

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?

Description uses specific verb 'Resend/nudge' and resource 'DocuSign envelope', with clear condition 'has not been signed yet.' This distinguishes it from siblings like send_for_signature or void_envelope.

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?

Provides clear context: the action targets an envelope that hasn't been signed yet, implying it should be used only for pending signatures. It doesn't explicitly name alternative tools, but the condition offers enough guidance.

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