kaiten_add_column_subscriber

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

No annotations are provided, so the description must fully disclose behavioral context, but it only restates that the tool adds a subscriber. It does not mention side effects, duplicate handling, permissions, notifications, or response behavior, leaving the mutation's consequences opaque.

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 clean, front-loaded sentence with no filler or redundancy. It is appropriately compact for a simple operation, though it could have used the space to add behavioral guidance without becoming verbose.

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 mutation with fully documented parameters, an agent can likely invoke it correctly with column_id and user_id. However, the lack of annotations and behavioral details such as optional type handling, side effects, or expected response leaves small but real gaps. It is minimally complete but not richly contextual.

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 input schema already documents all three parameters with 100% coverage, including the meaning of the type parameter (1=all, 2=mentions only, default 1). The description adds no additional parameter semantics, so the baseline of 3 is appropriate given the schema already carries the full burden.

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 states a specific action ('Add') and a specific resource ('subscriber to a Kaiten column'), making the tool's purpose immediately clear. It is naturally distinguished from sibling tools like kaiten_add_card_subscriber and kaiten_remove_column_subscriber because of the explicit 'column' target.

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 no guidance on when to use this tool versus alternatives such as adding a card subscriber or listing/removing column subscribers. An agent must infer usage from the tool name alone, with no explicit conditions, prerequisites, or exclusions.

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