check_tag_name

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

With no annotations, the description discloses key behavioral traits: it is asynchronous and returns a boolean via { exists: boolean }. This adds value beyond the name and gives the agent necessary information about execution and return format. It does not mention side effects (none implied) or error behavior, but the core traits are covered.

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, concise sentence that front-loads the primary action and includes the return type. There is no filler or redundant content; every word contributes useful information.

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 tool without an output schema, the description is complete: it explains the purpose, provides an example, notes async behavior, and specifies the return shape. It lacks edge-case details (e.g., case sensitivity) but these are not necessary for such a straightforward utility.

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 the parameter described as 'Tag name to check'. The description adds the example of 'artwork inventory numbers' but does not provide additional semantic detail such as case sensitivity, format, or length constraints. Baseline 3 is appropriate since the schema already fully documents the parameter.

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?

Description clearly states the tool performs an 'Async uniqueness check for a tag name' with a specific example use case. This distinguishes it from other tag-related tools like create_tag or get_tag by focusing on validation rather than mutation or retrieval.

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 implies the tool is used to check uniqueness before creating/updating a tag, and the example ('e.g., for artwork inventory numbers') provides context. However, it does not explicitly state when to use this vs. alternatives or mention any exclusion criteria, so the guidance is only implied.

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