join_channel

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

The description claims idempotency ('Idempotent when the account is already a member'), but annotations set idempotentHint=false. This contradiction undermines transparency. Additionally, destructiveHint=true conflicts with the safe join operation.

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?

Two sentences, no wasted words, front-loaded with the core action and key condition (non-archived, idempotent).

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?

The description covers the basic action and condition but omits details about preconditions (e.g., authentication, channel existence) and does not resolve the annotation contradiction. Output schema exists, so return values are handled elsewhere.

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 schema covers 100% of the single parameter 'channel' with description 'a string that will be trimmed'. The tool description adds no further semantics beyond the schema.

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 'Join a non-archived Huly channel', specifying the verb (join), resource (channel), and condition (non-archived). It distinguishes from siblings like 'leave_channel' and 'archive_channel'.

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 usage for joining a channel and notes idempotency, but does not explicitly exclude archived channels or mention alternatives. Sibling names like 'leave_channel' provide context.

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