superset_tag_delete

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

With no annotations, the description carries the burden and discloses key behavioral traits: the destructive side effect of removing all object attachments and the mandatory confirmation. It does not mention irreversibility or permissions, but these are implied by 'delete'. The confirmation requirement adds important safety context.

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 concise and front-loaded with the main action, followed by the side effect and a structured Args section. Every sentence adds value with no unnecessary fluff.

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 simple delete tool, the description covers the primary purpose, side effects, and parameter meanings. It lacks explicit detail about what happens if confirm_delete is false or if the tag does not exist, but the presence of an output schema mitigates the need to document return values.

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?

The description explains both parameters: tag_id as the ID to delete and confirm_delete as deletion confirmation. Since the input schema has 0% description coverage, this fully compensates. However, it declares confirm_delete as REQUIRED while the schema marks it optional with default false, creating a minor inconsistency.

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?

Description clearly states 'Delete a tag' with specific verb and resource, and adds the side effect that all object attachments will be removed. This distinguishes it from sibling tag operations like get, update, list, or bulk_create.

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?

Usage is implied by the delete action and the explicit requirement for confirm_delete, but no explicit alternatives or when-not-to-use conditions are provided. The confirmation requirement serves as a basic usage guideline.

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