list_bookings

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

With no annotations, the description carries the full burden for behavioral transparency. It only says 'list bookings with optional filters' and does not disclose authentication needs, data scope (e.g., current user only), pagination behavior, or read-only nature. This is insufficient for safe and effective agent usage.

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?

The description is extremely concise—one sentence with no superfluous words. It is front-loaded. However, it may be too brief given the tool's complexity and multiple parameters; a bit more structure could improve clarity.

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?

Despite the presence of an output schema, the description lacks critical context. It does not clarify the scope of the list (e.g., personal vs. all bookings), pagination details, or how this tool relates to similar ones. A more complete description would include such context to aid proper usage.

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 description coverage is 100%, so the baseline is 3. The description adds no meaning beyond the schema; it merely states 'optional filters' without elaborating on what filters exist or how they work. The schema already describes each parameter adequately, so the description provides negligible added value.

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 bookings and supports optional filters, which is a specific verb-resource combination. However, it does not differentiate from sibling tools like list_team_bookings or get_booking, which could cause confusion about scope.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't indicate that get_booking is for a single booking or that list_team_bookings is for team bookings. No exclusions or context are given.

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