tag_update

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

With no annotations, description carries full burden. Discloses critical behaviors: nil tagId may create new tag, tagItems replaces lists, tagType values, and that it is not yet live-tested. Could mention permissions or response, but overall strong.

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?

Concise single paragraph, no wasted words. Each sentence serves a purpose – purpose, prerequisite, enum values, replacement behavior, reliability warning. Front-loaded with purpose.

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 complexity (nested objects, no output schema, no annotations), description covers essential points: how to get tagId, tagType meaning, tagItems behavior, and testing caveat. Could mention optional organization_id and allTagItems parameter, but overall sufficient.

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%, baseline 3. Description adds significant meaning: tagId must be valid GUID, tagType enum values, tagItems replacement behavior. Does not add much for name, active, or organizationId, but the added info for key parameters is valuable.

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?

States 'Update Tag. Updates an existing tag' – clear verb and resource. Distinguishes from sibling tools like tag_get_by_id by focusing on update. However, could be more specific about which fields are updatable beyond items.

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?

Explicitly recommends using tag_get_dropdown_options_by_organization_id to discover tag GUIDs first. Warns about nil tagId causing creation. Lacks explicit exclusions or when to use alternatives, but provides solid context.

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