Book Course

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

With annotations already indicating a non-read-only, non-idempotent operation, the description adds real-world side-effect context ('real student account') and discloses the postcondition ('verify it with a fresh enrolled-course read'). It also surfaces the important non-behavior that conflict checks are not implicit. More depth about failure states or permission requirements would improve it, but this is still strong.

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, information-dense sentences. The first states the action and verification, and the second adds the conflict-check caveat. No filler or repetition of schema details.

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?

For a single-parameter booking tool, the description covers the core operation, the verification step, and the conflict-checking caveat. It does not explain the return shape or error conditions, but there is no output schema to mirror, and the overall complexity is low.

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 gives only courseId with minLength; the description adds that it is a 'learning-unit course ID', which is helpful, but it does not specify where the ID comes from or that it should be a bookable course. With 0% schema description coverage, more explicit parametric guidance would be beneficial, yet the single param's role is largely inferable from the tool name and description.

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 states a specific verb-resource pair: book a learning-unit course on the real student account. It also names the follow-up verification action and implicitly separates this tool from siblings like unbook_course, check_course_conflicts, and join_waitlist.

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 explicitly warns that it does not check conflicts and directly instructs the agent to call check_course_conflicts first when schedule compatibility matters. This provides clear when-to-use versus when-to-defer-to-another-tool guidance.

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