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

Annotations already declare readOnlyHint and destructiveHint as false, so the description adds little behavioral context beyond stating it lists bookings. No mention of pagination, sorting, or rate limits. 3 is appropriate as it does not contradict annotations.

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 front-loads the key purpose and optional parameters. No filler words, all information is relevant and well-structured.

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 simple list operation, the description covers the main purpose and parameters. It does not describe the return format (e.g., list of booking objects) but given the lack of output schema and standard nature, this is acceptable. Minor gap in not specifying response structure.

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 schema coverage at 0%, the description adds meaning by stating that status filters bookings and sessionId optionally scopes them. However, it does not specify allowed status values or the format of sessionId. Adds value but lacks details.

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 it lists authenticated user's one-on-one session bookings, filterable by status and optionally by session. This distinguishes it from siblings like list_session_bookings (likely admin view) and other booking tools.

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 implies usage for viewing one's own bookings but does not explicitly state when to use this versus alternatives like list_session_bookings or cancel_session_booking. No exclusion criteria or prerequisites are mentioned.

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