Delete Signature

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

The description states 'This cannot be undone' and 'Permanently removes', which aligns with the annotations (destructiveHint=true). However, the annotations already convey destructive behavior, so the description adds only emphasis, no new behavioral insights beyond what annotations provide.

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 starts with a clear statement of purpose but becomes redundant, repeating the deletion message and the note about irreversibility. It includes the endpoint, which is helpful but not essential. Could be tighter.

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 delete operation, the description provides basic context (action, parameters, endpoint) and links to 'Field Productivity'. However, it omits details like required permissions, impact on related data, or how it fits with other signature deletion tools. Adequate but not comprehensive.

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 parameter descriptions already present. The description merely repeats that project_id and id are required, adding no additional meaning about the parameters' roles or constraints.

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 tool deletes a signature for a given ID and mentions the resource ('Field Productivity records'). It provides the endpoint, which adds specificity. However, it does not explicitly distinguish from sibling tools like delete_signature_project_v1_0 or delete_a_signature, leaving some ambiguity.

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 says 'Use this to permanently delete the specified Field Productivity records' and lists required parameters. It gives basic usage context but does not mention when not to use this tool or provide alternatives among the many delete signature siblings.

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