airbyte_delete_tag

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

Annotations already indicate destructive= and idempotentHints. The description adds crucial detail: 'This is a permanent operation. The tag will be removed from all resources it was attached to.' No contradictions with 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 concise: a single-line statement, a usage guideline, and an example. No superfluous text.

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 with one parameter and an output schema, the description covers purpose, effect, usage context, and example thoroughly.

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 schema has a nested parameter with some description. The description adds an example UUID format, but most parameter semantics are already clear from the schema.

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 clearly states 'Delete a tag by its UUID', providing a specific verb and resource. It distinguishes from sibling tools like create_tag or update_tag.

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?

It includes a 'When to Use' section with a clear example: 'Remove an obsolete or duplicate tag.' This is helpful but could be more explicit about when not to use it.

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