airbyte_create_tag

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

The annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds the return value ('The created tag with its tagId') and an example, but does not disclose other behavioral aspects like permissions or side effects beyond creation. It does not contradict the 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, well-structured with clear sections (title, When to Use, Returns, Example), and uses fewer than 50 words. Every sentence is informative without redundancy.

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 (one required param, one optional, with output schema), the description provides purpose, usage guidance, return value, and an example. It lacks mention of any prerequisites or error handling, but is largely complete for basic use.

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 description coverage is 0% according to context, yet the description only provides an example for the 'name' parameter and does not explain the 'response_format' parameter. The schema itself describes 'name', but the description adds minimal value beyond that. More parameter explanation is needed.

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 'Create a new tag in Airbyte.' and adds that it is used to 'Add a new organizational label for resources.' This is a specific verb (create) and resource (tag), and it distinguishes from siblings like airbyte_delete_tag or airbyte_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?

The 'When to Use' section explicitly says 'Add a new organizational label for resources.' This provides clear guidance on when to invoke the tool. However, it does not mention when not to use it or alternatives.

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