Join Waitlist

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

Annotations already indicate a mutation (readOnlyHint=false). The description adds useful behavioral context by specifying it operates on the 'real student account' and that it will re-read the catalog to report the resulting position. No contradictions with annotations, but it does not disclose edge cases like duplicate join attempts or failure handling.

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?

A single concise sentence that leads with the primary action and includes the follow-up read. No wasted words or redundant information.

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 touches on the main action and the reporting step, but with no output schema it should specify the return format or result structure. It also omits common edge cases (e.g., already on waitlist, course not available). For a simple mutation tool, this is adequate but not thorough.

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?

With 0% schema description coverage, the description must explain the parameter. It only implies courseId is the course to join via the phrase 'Join a course waitlist' but never explicitly maps it or describes how to obtain the ID. This leaves the parameter under-explained for a tool with a single required param.

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 a specific verb (Join) and resource (course waitlist) and adds a secondary action (re-read booking catalog) that differentiates it from siblings like book_course and leave_waitlist. It is unambiguous what the tool does.

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 provides no explicit guidance on when to use this tool versus alternatives such as book_course or leave_waitlist. It does not state conditions like 'use when a course is full' or 'when not already enrolled,' leaving usage context to inference.

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