sigma_delete_tag

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the requirement that confirm=True is necessary, which is a behavioral constraint beyond the schema's default. This prevents accidental deletion and aligns with the destructive nature of the operation.

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 two short sentences: 'Delete a tag. Requires confirm=True.' Every word earns its place, with no redundancy or irrelevant detail.

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?

With only two parameters (one required) and an output schema available, the description covers the essential aspects: what the tool does and the mandatory confirmation. It does not elaborate on edge cases or error behavior, but for a simple delete operation, this is adequate.

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 description coverage is 0%, so the description must compensate. It explains that confirm must be true, which clarifies the boolean parameter's role. However, tag_id is not described, but its meaning is apparent from the context. This partial compensation yields a score of 3.

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 states 'Delete a tag.' which uses a specific verb (delete) and resource (tag). This clearly distinguishes it from sibling tools like sigma_delete_file and sigma_delete_workspace, which target different resources.

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 provides a clear usage guideline: 'Requires confirm=True.' This tells the agent that the confirm parameter must be set to true for the deletion to proceed. It does not explicitly mention alternatives, but the resource is unambiguous, and the confirm requirement is valuable operational context.

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