cigchat_subscriber_assign_agent

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

With no annotations provided, the description must disclose behavioral traits. It adds the auth requirement ('Manage Flow' scope), which is useful. However, it does not mention whether the assignment overwrites an existing agent, idempotency, or what happens on success/failure.

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, front-loaded sentence that communicates the action and a key requirement without wasted words. It is appropriately concise.

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 lack of annotations, output schema, and a partially documented parameter set, the description is too minimal. It omits essential context about the user_ns parameter, return values, and side effects, leaving the agent with incomplete guidance for a mutation 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?

The description adds no parameter information. The schema covers agent_id (50% coverage) with a helpful description, but user_ns is undocumented in both schema and description. Since schema coverage is not high and the tool description offers no compensation, parameter semantics are weak.

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: 'Assign agent to chat' with the HTTP endpoint. It distinguishes the tool from siblings like 'cigchat_subscriber_unassign_agent' and 'cigchat_subscriber_assign_agent_group' by specifying it assigns an individual agent to a chat.

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 gives clear context (assigning an agent to a chat) and a prerequisite (requires 'Manage Flow' scope), but does not explicitly mention when to use this tool versus alternatives such as 'assign_agent_group' or 'unassign_agent'. No exclusions or alternative guidance are provided.

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