list_my_bookings

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful default behavior (from_date defaults to today) and the idea of a forward-looking window, but says nothing about result volume, ordering, or how building_id affects behavior.

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?

One sentence, no filler, with the format and default for the key parameter front-loaded. Slightly awkward phrasing ('from from_date ... over `days` days') costs a point but nothing is wasted.

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?

For a simple read-only listing tool with no output schema, the core invocation semantics are present. The omission of building_id's filter effect is the main gap an agent would hit in practice.

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 0%, so the description must carry parameter meaning — it does explain from_date's YYYY-MM-DD format and today default, and gestures at `days`. However, the third parameter building_id is never mentioned and 'over `days` days' is ambiguous about whether it is a window length or a count.

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?

States a specific verb and resource ('List the user's bookings') and scopes it to the caller's own bookings, which separates it from search_spaces/list_locations. It does not mention cancel_booking or book_space, but the read-only listing intent is unambiguous.

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 on when to use this versus siblings such as search_spaces, or when to prefer a wider date window. The only implicit cue is 'the user's bookings', which signals personal scope but gives no exclusions or alternatives.

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