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

Discloses critical behaviors such as preferring certain peers, fallback behavior, returning existing rooms, and never creating synthetic agents. Since annotations only indicate idempotent and open world, this enriches the agent's understanding of side effects.

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 sentences cover all essential info without fluff, front-loading the primary action and behavior, and preserving conciseness while conveying depth.

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?

Given no output schema, the description explicitly covers what happens in edge cases (already paired), fallback logic, and constraints, making it self-sufficient for the agent.

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 fully describes the agent_key parameter, so description adds nothing new about it. Its main focus is on behavior, which is appropriate since the only parameter is straightforward.

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?

Verb 'join' is specific and the resource is the speed-dating queue. Precisely distinguishes from siblings like speedbot_leave and speedbot_rooms, making selection unambiguous.

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?

Clearly explains the tool's purpose and behavior, and implies it is the correct choice for joining the queue. However, it does not explicitly state when NOT to use it or mention alternatives, which would elevate it further.

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