create_tag

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

Annotations provide idempotentHint=false and destructiveHint=false, but the description adds crucial context: creating is not destructive, and if the tag exists, it returns the existing one. This clarifies safety and non-destructive behavior beyond 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 but includes a brief introduction about tags that could be separated. It is front-loaded with the key behavior and functional, though slightly verbose for an expert agent.

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 create tool with no output schema, the description covers idempotency and basic behavior. It lacks explicit mention of return value or uniqueness constraints beyond the existence check, but is largely complete for the tool's complexity.

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% with descriptions for both name and description. The description does not elaborate on parameter usage beyond the schema, so it adds minimal extra meaning. 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 clearly states 'Create a new tag' and explains what a tag is, distinguishing it from sibling tools like list_tags, get_tag, etc. It also mentions idempotent behavior when name exists, making the purpose very specific.

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 describes when to use (create a tag) and hints at a get-or-create pattern, but does not explicitly state when not to use or suggest alternatives like update_tag or get_tag. The guidance is implicit and lacks explicit exclusion.

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