delete-trace-tag

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

The tool's annotations include destructiveHint=true, indicating a write operation. The description adds that it removes a tag, which is consistent. However, it does not disclose behavior like whether it succeeds if the tag does not exist, or if it is idempotent. The description does not contradict annotations.

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 a single sentence, efficient and to the point. It is concise but could be more informative without being verbose, e.g., mentioning the return value or idempotency.

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 tool's simplicity (2 required parameters, no output schema), the description covers the basic action. However, it lacks information about the return value (e.g., success indicator) and error conditions, which would be helpful for an AI agent. It is minimally 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?

The input schema has two parameters: traceId (no description) and key (description: 'Tag key to remove'). The tool description does not add any meaning to the parameters beyond what the schema already provides. Since schema coverage is only 50% (key described), the description should compensate but does not.

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 'Remove a tag from a trace' clearly states the action (remove) and the resource (tag from a trace), distinguishing it from siblings like 'set-trace-tag' that add/update tags. However, it could be more specific by noting that it removes a specific tag by key, matching the parameter 'key'.

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 no guidance on when to use this tool versus alternatives like 'set-trace-tag' or other tag delete tools ('delete-run-tag'). It only states the action, with no when-to-use or when-not-to-use information.

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