delete_signature_request

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 does not mention irreversibility, side effects on related records, required permissions, or any other behavioral traits beyond the obvious 'delete' action. For a deletion tool, this is a significant omission.

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 a single, efficient sentence with no wasted words. While it lacks detail, it is appropriately concise for the surface-level purpose it communicates.

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 closely related sibling tools such as 'cancel_signature_request' and the absence of an output schema, the description is incomplete. It does not explain the distinction between deletion and cancellation, or the impact on associated data, which is essential for correct tool selection in this 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 input schema already provides 100% coverage with descriptions for both required parameters ('Signature request ID' and 'Contract ID'). The description adds no additional parameter meaning, but the schema is sufficient, so the baseline score of 3 applies.

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 verb (delete) and resource (signature request), making the primary purpose unambiguous. However, it does not distinguish this from the sibling tool 'cancel_signature_request', so the purpose is clear but the differentiation is weak.

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 like 'cancel_signature_request' or 'delete_signature_request_recipient'. There are no prerequisites, exclusions, or recommended usage contexts, leaving the agent without decision support.

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