update_tag

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

With no annotations, the description carries full behavioral disclosure burden. It only states it's an update with partial changes, but omits details like return value, error handling, authorization, or reversibility. The presence of an output schema is not mentioned.

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 extremely concise with a single, front-loaded sentence containing the essential action and partial update behavior. However, it could be slightly expanded to mention the output or a hint without losing conciseness.

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 has 7 parameters, no schema descriptions, and no annotations, the description is too sparse. It does not cover return values, error scenarios, or parameter relationships. The existence of an output schema reduces the need for return value explanation, but overall completeness is low.

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%, yet the description adds no explanation for any of the 7 parameters (name, slug, tag_id, etc.). It fails to compensate for the lack of schema descriptions, leaving parameter meaning entirely to the schema property names.

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 the action (Update), the resource (a tag), and the identifier (by id). It also specifies partial update behavior ('only the fields you pass are changed'), distinguishing it from create, delete, or full replacement tools.

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 use for modifying existing tags but does not explicitly mention when to use this tool over siblings like delete_tag or create_tag. No alternatives or when-not-to-use guidance is provided.

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