asana_remove_tag

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

The description does not contradict annotations and simply states the core action. It adds no information beyond what is already in the annotations, such as operation side effects, failure behavior, or whether the tag must already be attached to the task. With annotations present, the description could have offered more context but does not.

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, compact sentence that front-loads the verb and object. It is minimal without being under-specified, and every word contributes meaning.

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 tool with two clearly described GID parameters and no output schema, the description/schema combination is sufficient for an agent to invoke it correctly. It only lacks optional nuances like behavior when the tag is not currently on the task, which are not critical for basic operation.

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 100% for both parameters, each described as 'Task GID' and 'Tag GID'. The description does not add any further meaning about parameter formats, relationships, or expected inputs. It neither improves nor harms parameter understanding.

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 verb 'Remove', the resource 'tag', and the target 'task'. This distinguishes it from closely related sibling tools like asana_add_tag and asana_remove_follower, so there is no ambiguity about what the tool does.

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 provides no guidance on when to use this tool versus alternatives such as asana_add_tag or when a specific condition should be checked first. Usage is only implied by the tool name and the simple operation description.

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