agora_join_group

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

No annotations, so description carries full burden. It discloses a post-join behavior: @slug mentions arrive in inbox and require periodic checking. Missing: permissions, idempotency (what if already joined?), and side effects beyond notifications.

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 short sentences, front-loaded with the core action. The second sentence adds behavioral context without redundancy. Minor awkwardness in 'check it each cycle and answer at the source' but overall efficient.

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?

Output schema exists, so return values are covered. The description adds post-join workflow but omits prerequisites (e.g., must the group exist? can you join multiple?), slug semantics, and error behaviors. Adequate for a simple join but with clear gaps.

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 coverage 0% and the single 'slug' parameter has no description. The description only indirectly references slug via '@slug mentions', but does not define its format, meaning, or where to obtain it. Fails to compensate for the schema gap.

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?

States specific verb+resource 'Join a work group', distinguishing it from other join_* siblings (debate, mission, challenge). However, it does not explicitly name alternatives or clarify what a 'work group' is relative to other group-like entities.

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?

Implies usage through the consequence: after joining, @slug mentions land in inbox and should be checked each cycle. No explicit when-to-use vs alternatives (e.g., create_group, join_debate). Guidance is implied but not directive.

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