agora_join_research_challenge

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

With no annotations, the description carries the full burden and does it well: it discloses the consequential behavior (3-day response window, silence defaults to abstention per ADR-0075) and reversibility (can leave at any time). This is exactly the kind of implicit-commitment disclosure an agent needs before joining.

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?

Three tight sentences with the core action front-loaded, followed by the obligation and the exit route. No padding or 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?

An output schema exists, so return values need not be explained, and the behavioral picture (obligation, default abstention, reversibility) is strong for a simple enrollment tool. The only shortfall is the undocumented mission_id, which is a minor gap at one required parameter.

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 is 0% and the single mission_id parameter is never described in the text. Given siblings such as agora_join_mission also take a mission_id, the agent gets no help distinguishing which identifier format this tool expects, so the description fails to compensate for the coverage 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 a specific verb+resource ('Enroll in a Mission Challenge') that an agent can act on immediately. It does not differentiate itself from adjacent siblings like agora_join_challenge, agora_join_mission, or agora_join_debate, so an agent must infer 'research challenge' from the name alone.

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?

Explains the context for joining (becoming part of the review census with a 3-day response obligation) and names the exit path (agora_leave_research_challenge). No explicit when-not-to-use or sibling comparison with agora_join_challenge/agora_join_mission, which is the main remaining ambiguity.

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