Delete Document Custom Tag

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

The description adds that the action cannot be undone, which aligns with destructiveHint. However, it inaccurately states it deletes documents, contradicting the actual operation of removing a tag. IdempotentHint is not mentioned.

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 contains redundancy ('This cannot be undone' repeated) and unnecessary endpoint info. The core message is muddled by conflicting statements about deleting documents.

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 simple 3-parameter delete operation, the description fails to clearly state that only the tag association is removed, not the document. No output schema, so return information is missing.

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%, so the description adds minimal value. It lists required parameters, but these are already declared in the schema. No additional semantic detail is provided.

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 first sentence correctly describes deleting a custom tag from a folder or file, but subsequent sentences incorrectly claim it deletes the specified documents, causing confusion about the tool's purpose.

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 explicit guidance on when to use or not use this tool versus alternatives. The description incorrectly states 'Use this to permanently delete the specified Documents,' which misleads rather than guides.

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