conversations_join

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

With no annotations, the description must fully disclose behavior, but it only states 'Join an existing conversation.' It fails to mention effects (e.g., user becomes a member), error conditions (e.g., already a member), or required permissions. This leaves the agent with significant uncertainty.

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 very short (one sentence), which is concise but at the cost of necessary detail. It lacks important context that could be added without significant bloat, making it under-specified rather than optimally 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?

While the presence of an output schema reduces the need to describe return values, the description still omits many relevant details such as what happens on success, common errors, or usage context (e.g., public vs private channels). For a simple tool, it is not complete enough.

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 sole parameter 'channel' has no description in the schema (0% coverage), and the tool description provides no additional meaning. It does not explain whether 'channel' expects an ID or name, its format, or any constraints.

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 ('Join') and resource ('existing conversation'), which distinguishes it from tools like 'conversations_leave' or 'conversations_create'. However, it does not differentiate from similar tools like 'conversations_open' or 'conversations_invite', which could cause confusion.

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. For example, it does not clarify scenarios where 'conversations_open' or 'conversations_invite' might be more appropriate, nor any prerequisites for joining.

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