delete_tag

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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the mutation safety profile. The description adds no further behavioral context (e.g., reversibility, cascading effects, or error behavior). Since the annotation provides the key disclosure, the description adds limited value but does not contradict.

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?

Two concise sentences with zero redundancy. The purpose is stated clearly, and the required parameter is called out. Every word serves a purpose, making it highly efficient.

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 one-parameter destructive action, the description covers the core purpose and required input. However, it lacks usage guidelines and any note on what happens if the tag does not exist or has dependencies. Given the low complexity, it is minimally adequate but not fully complete.

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%: the parameter tagName already has a description ('Tag name to delete.'). The description repeats this and notes it is required, but adds no additional semantics such as constraints or examples. Baseline 3 applies because the schema does the heavy lifting.

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?

States a specific verb ('delete') and resource ('a tag from your SimpleLocalize project'). The purpose is clear and unambiguous. It does not explicitly contrast with sibling tools like update_tag or create_tag, but the action is distinct enough that an agent can infer when to use it.

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 guidance on when to use this tool versus alternatives. It does not mention when to prefer delete_tag over create_tag or update_tag, nor when not to use it. The only context is the purpose statement, leaving the agent to infer usage from the name.

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