Booking report

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 genuinely useful behavioral detail by disclosing that results are grouped counts by status (finished, cancelled, noShow, upcoming) and by booking page, which tells the agent what the response will contain. It stops short of describing pagination or whether both groupings are always returned.

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?

Two tight sentences, front-loaded with what is counted and grouped before the example query. No filler and every clause adds information.

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 read-only aggregation tool with no output schema, the description conveys the essential return shape (counts by status and booking page) and the period requirement. It could say more about the exact response structure and the role of bookingPageIds, but nothing critical to invoking it correctly is missing.

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 coverage is 67%: from/to are well documented in the schema, but bookingPageIds has no schema description. The phrase 'by booking page' hints that this parameter scopes or groups by page, adding marginal meaning, but it does not explain the array semantics or filtering behavior. Baseline 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?

States a specific verb (counts) plus the resource (bookings) and the exact grouping dimensions (status and booking page). An agent can immediately separate this aggregate-report tool from the sibling listing tools like search_bookings or list_upcoming_bookings.

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 example question ('how many no-shows did we have last month?') clearly signals the intended usage context for a counting/aggregation query. However, it never names an alternative tool or states when not to use it, so the routing guidance is implied rather than explicit.

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