Delete Checklist Signature

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

Beyond the destructiveHint and idempotentHint annotations, the description discloses that deletion is permanent, cannot be undone, and a repeat call returns 404. It also details common error statuses (401, 403, 404) and their meanings, adding valuable behavioral context not present in annotations.

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 largely efficient and front-loaded with the main action, but includes a redundant 'Required parameters' line that duplicates the schema. The API context and error handling are useful, though the description could be slightly trimmed without losing value.

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?

Covers purpose, prerequisites, permanence, idempotence behavior, error handling, and API location. For a delete tool with no output schema, this is complete and leaves no critical gaps for an agent to select and invoke it correctly.

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 coverage is 100% with each parameter described. The description adds extra semantics by emphasizing that list_id and signature_request_id must identify existing parent records and should be resolved via list tools, which is not explicitly in the schema. It also reinforces the endpoint path structure.

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 'Deletes a Signature for a specified Checklist Signature Request' with a specific verb and resource. It distinguishes from the sibling 'delete_checklist_signature_request' by specifying it deletes the signature, not the request. The endpoint path further clarifies the exact operation.

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 explicit preconditions: confirm the target id with the matching show/list tool and resolve parent records first. This gives clear context on when to use this tool, though it doesn't name alternative tools or explicitly state when not to use it. The purpose statement inherently differentiates from siblings.

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