add_tag

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

With no annotations, the description carries the full burden. It discloses one behavioral trait ('creates tag if it doesn't exist'), which is helpful, but it does not address what happens if the tag already exists on the item, whether the item must exist, or permissions. This is a minimal but useful disclosure.

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?

Single sentence, front-loaded with the action, and includes a relevant parenthetical without any fluff.

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?

The description covers the core action and one side effect, but for a mutation with no annotations and no output schema, it could also mention failure modes or return behavior. It is adequate for a simple tool but incomplete for a fully self-sufficient description.

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 placeholder descriptions ('item_id parameter'), and the tool description doesn't add meaningful clarification beyond the parameter names. Since schema coverage is 100% (even if weak), the baseline is 3.

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 uses a specific verb ('add') and resource ('tag to an item'), clearly defining the operation. It distinguishes from sibling tools like remove_tag, update_tag, and delete_tag, and the parenthetical adds a useful detail about tag creation.

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 when to use this tool (when adding a tag to an item) but does not explicitly state alternatives or exclusions. There is no mention of when not to use it or how it differs from other tag-related tools.

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