aidoo_list_bookings

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

No annotations are provided, so the description must carry the full burden. It only says 'list or filter' without disclosing behavior like pagination (limit/offset), default result size, how filters combine (AND/OR), or that extensions modify response content. This is insufficient for a tool with 8 parameters and no output schema.

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 a single, concise sentence in German that quickly conveys the primary purpose. It is not overly verbose, but given the tool's complexity, it could arguably include more structure. However, it is clean and front-loaded, earning a 4.

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?

With 8 parameters, no annotations, and no output schema, the one-line description is wholly inadequate for understanding the tool's full behavior. It does not explain how filters work, what the response format is, or the meaning of the 'extensions' parameter, making it incomplete for real-world use.

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 description coverage is 100%, so every parameter (id, limit, offset, etc.) has a meaningful description. The tool description adds only generic 'filter by criteria' which does not enrich the schema. Since the schema already provides full parameter semantics, the baseline score of 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 clearly states it lists bookings ('Liste alle Buchungen auf') with optional filtering ('oder filtere nach Kriterien'). This distinguishes it from sibling tools like aidoo_get_member_bookings (specific member), aidoo_create_booking, and aidoo_cancel_booking by emphasizing the general listing capability.

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 use cases (list all or filter), but does not explicitly mention when to choose this over alternatives such as aidoo_get_member_bookings or aidoo_get_schedule. There is no exclusion or comparative guidance, so it meets the bare minimum but lacks direct sibling differentiation.

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