Delete tag

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

Annotations already indicate destructive and idempotent behavior, but the description adds no further insight into side effects, permissions, or consequences (e.g., whether deletion cascades to tagged devices). The endpoint detail is not behavioral.

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 first two sentences are redundant, repeating 'Delete tag' / 'Deletes a tag'. This wastes space and adds no value. The structure is not front-loaded with unique information.

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 destructive nature, the description should explain what happens to tag-device relationships or any prerequisites. It also does not distinguish from sibling tools like removeTagFromDevices. The lack of an output schema is fine, but the behavioral context is incomplete.

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 input schema covers the single 'id' parameter with a clear description, achieving 100% schema_description_coverage. The tool description adds no extra parameter semantics beyond the schema, so baseline 3 is appropriate.

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 'Delete tag. Deletes a tag.' essentially restates the tool name and title, providing no new information about scope or behavior. The API endpoint line adds a technical reference but does not clarify what the deletion entails (e.g., permanent removal, effect on device associations).

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?

There is no guidance on when to use this tool versus related operations such as removeTagFromDevices, which handles detaching tags from devices. The description lacks any contextual or alternative usage directions.

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