cigchat_subscriber_unsubscribe_from_bot

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

With no annotations, the description carries the full burden, but it only discloses the required scope and HTTP method. It does not explain side effects (e.g., whether this permanently stops all communications), reversibility, or any additional behavioral implications beyond the generic 'unsubscribe'.

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 with no filler. Including the HTTP endpoint and scope requirement is concise and functional, earning its place without redundancy.

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 (1 param, no output schema) and absent annotations, the description is too minimal. It lacks parameter semantics, expected behavior on success/failure, and any clarification of what 'unsubscribe' actually entails, leaving significant gaps for an agent.

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% and the description provides no explanation of the required 'user_ns' parameter. The agent receives no help understanding what this parameter means or how to populate it, so the tool is difficult to invoke correctly.

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: 'Unsubscribe from bot', which is a specific verb+resource. It is distinct from sibling tools like subscribe_to_bot, opt_out_email, and opt_out_sms, and the endpoint DELETE /subscriber/unsubscribe-from-bot adds technical clarity.

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?

No guidance is provided on when to use this tool versus alternatives such as pause_bot or opt_out_email/opt_out_sms. The only condition mentioned is the 'Manage Flow' scope requirement, but there is no situational context or differentiation from other subscriber tools.

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