Delete Stamp

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

Annotations already provide destructiveHint=true, and the description reinforces irreversibility and specifies what gets deleted (Document Markup records). This adds context about the scope (company, project, document) beyond 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 somewhat redundant, repeating 'Permanently removes' and 'This cannot be undone' twice. Could be more concise by merging sentences and omitting endpoint details if they are not essential for the agent.

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 tool with no output schema, the description covers purpose, required parameters, irreversibility, and scope. It is fairly complete, though it does not mention success response or side effects (but that is typical for deletes).

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 descriptions for each parameter. The description only reiterates that parameters are required and lists them, adding no new semantic meaning beyond the schema.

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 it deletes a stamp for a specific company, project, and document. It distinguishes from sibling tools like 'remove_an_existing_markup' by specifying 'stamp' and 'Document Markup records', making the resource clear.

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 explains when to use it (to permanently delete stamps) and warns it cannot be undone, but does not explicitly mention alternatives or when not to use it. Guidelines are implied by the scope but not explicit.

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