unassign_tag

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states the required role (collaborator/admin) and clearly implies a mutating action via 'unassign'. It does not cover edge cases or return values, but for a simple unassignment, the key behavioral constraint is disclosed.

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?

A single, efficient sentence that front-loads the action and includes a necessary permission note. No wasted words; every element earns its place.

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 simplicity of the operation (two documented parameters, no nested objects, no output schema), the description provides the core purpose and authorization context. It is sufficiently complete, though details about error handling or idempotency could enrich it further.

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%, so both parameters are already explained in the input schema. The description does not add extra meaning beyond what the schema provides, but the baseline of 3 applies because the schema itself is sufficient.

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 tool 'unassigns a tag from a post', using a specific verb and resource. It naturally distinguishes itself from assign_tag and other tag-related operations. The role requirement adds specific context.

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 usage is evident from the verb 'unassign' – this tool is for removing a tag from a post. The collaborator/admin role requirement provides an explicit access constraint, acting as a clear 'who can use' exclusion. No explicit alternative tools are mentioned, but the context is clear.

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