List bookings

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

The description implies a read operation, but without annotations it does not explicitly state idempotence or safety. It mentions ordering and lists bookings, which is fairly transparent, but lacks details on pagination, return format, or side effects.

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 very concise (one sentence) but at the cost of omitting important details. It earns its place but could be expanded to include parameter info and usage context.

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 no output schema and no annotations, the description is insufficient. It does not mention that all bookings are listed, how to paginate, or what fields are returned. The tool's behavior is incomplete for an AI agent to use confidently.

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?

Parameter description coverage is 0%, and the tool description does not explain the purpose or usage of 'limit' and 'offset'. The description entirely fails to add meaning beyond the schema's basic type constraints.

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 the property's bookings ordered newest first. It uses a specific verb ('list') and resource ('bookings'), and the ordering distinguishes it from other tools like search_availability.

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 given on when to use this tool vs alternatives such as get_booking (single booking) or search_availability (filtered search). The description fails to mention that it lists all bookings with no filtering capability.

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