cigchat_subscriber_unassign_agent

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

No annotations are provided, so the description carries the full burden. It discloses the required 'Manage Flow' scope, which is useful, but it does not mention side effects, reversibility, or what happens to the chat after unassignment.

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 one efficient sentence that includes the operation, endpoint, and auth requirement. Every word contributes value with no filler.

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?

With no annotations, no output schema, and zero parameter semantics, this description is incomplete. It covers purpose and auth but leaves the required parameter and expected response/effects undisclosed.

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 single required parameter 'user_ns' has no description in the schema and is not explained in the tool description. The agent cannot infer what value to supply or how to obtain it.

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 and resource ('Unassign agent from chat') and clearly distinguishes this from the sibling tool 'cigchat_subscriber_assign_agent'. The HTTP endpoint is also stated, adding precision.

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 the tool ('Unassign agent from chat') and includes the required scope, but it does not explicitly mention alternatives or when not to use it relative to other subscriber tools.

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