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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description's mention of filters adds minimal behavioral transparency. No additional traits (e.g., pagination behavior, rate limits, default sorting) are disclosed beyond what annotations provide.

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 sentence that is clear and to the point. No unnecessary words or redundancy. It front-loads the purpose and lists filters efficiently.

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 an output schema exists, return values need not be explained. The description combined with schema and annotations adequately covers the tool's functionality, though it could mention default behavior (e.g., limit 20) or that bookings are from the current company context. Still, it is sufficiently complete for an 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?

Schema coverage is 100%, so the input schema already describes all 7 parameters with descriptions. The description only summarizes some filter types without adding new meaning or clarifying any ambiguous parameter relationships. Baseline 3 is appropriate.

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 uses specific verb 'List' and resource 'bookings', and explicitly mentions filters (date range, status, service, staff, or member). This clearly distinguishes it from sibling tools like create_booking, cancel_booking, or other list 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 the tool is used for listing bookings with filters but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, though the context of siblings offers many list tools.

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