list_bookings

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

With no annotations, the description carries the full burden. It discloses pagination behavior ('Returns up to 10 records per page; increase skip by 10'), the entity's field categories, and the list of statuses. It doesn't cover auth or error behavior, but for a read-only listing tool this is reasonably transparent.

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?

Every sentence earns its place: purpose, entity explanation, use-case guidance, status enum, and pagination. It is front-loaded with the primary action and stays concise given the domain richness.

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 is complete for a one-parameter, no-output-schema tool: it explains what a booking is, key fields, statuses, and pagination. It doesn't describe return format, but that's not required when no output schema exists, and the content is sufficient for an agent to invoke it correctly.

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 already describes the skip parameter (100% coverage), and the description adds meaningful usage detail: 'increase skip by 10 to fetch the next page'. This clarifies the exact pagination mechanism beyond the schema's 'Number of records to skip'.

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 'List bookings (rental/trip records) for the API key account' with a specific verb and resource. It goes further to distinguish itself from siblings by explaining what a booking is and positioning it as the 'best object for who had which vehicle, and when?'.

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?

Provides clear usage context: 'Best object for who had which vehicle, and when?' and describes the scope as 'for the API key account'. It does not explicitly mention when not to use it or contrast with siblings like list_active_bookings, but the distinction is reasonably implied.

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