get_bookings

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

With no annotations, the description must fully disclose behavioral traits. It implies a read-only operation via 'Get' but does not explicitly state whether it is safe, what response format to expect, or any side effects. Pagination behavior and error handling are also omitted.

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 concise and front-loaded with the main purpose, followed by a clean parameter list. No unnecessary words or repetition, though the formatting could be slightly more polished with markdown.

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 covers the core functionality and filters, and an output schema exists to explain return values. However, it lacks usage guidance relative to get_booking_stats and does not mention pagination behavior or any limitations, leaving the context incomplete.

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 description manually lists each parameter with a default or semantic meaning, such as 'status: Filter by payment status' and 'event_id: Filter by specific event ID', which compensates for the 0% schema description coverage. The schema only provides types and defaults, so the description adds useful context.

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 the tool retrieves event bookings with filtering, which identifies the primary function and resource. However, it does not explicitly differentiate from the sibling tool get_booking_stats, though the resource names are distinct enough.

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 the sibling get_booking_stats. There is no mention of alternatives, prerequisites, or typical scenarios, leaving the agent without direction for tool selection.

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