List Bookings

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

The description reveals default compact view behavior and that include_charges implies full=true, adding behavioral context beyond the readOnly, idempotent, and openWorld annotations. No contradictions with annotations exist.

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?

Four crisp sentences cover the core purpose, a key requirement, default behavior, and optional flags. Every sentence adds value without repetition.

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 having 8 parameters and no output schema, the description effectively conveys the mandatory filter, view defaults, and related flag behavior. It relies on schema for details like status and date filters, which is acceptable given high schema coverage, though it could mention how status interacts.

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 covers 75% of parameters with descriptions, so baseline is 3. The description adds the cross-parameter constraint 'requires property_ids OR since_utc' and explains limit usage, which are not evident from the schema alone.

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 a specific verb 'Search' with resource 'bookings', clearly indicating a search/list operation. It does not explicitly differentiate from sibling tools like ownerrez_get_booking, but the name and phrasing imply a listing action.

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?

It states a clear prerequisite: requires property_ids or since_utc, and offers practical guidance on full view and limit. However, it does not mention when to choose alternative tools, so no explicit when-not guidance.

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