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

Annotations only declare readOnlyHint=true; the description adds real context beyond that — audience restriction (signed-in business owners), result ordering (pending requests first, then remaining bookings), default window, and inclusion of client contact details. It stops short of describing pagination or result limits, so not a 5.

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 sentences, both dense with actionable content: the first covers audience, ordering, defaults and return content; the second covers use cases and alternatives. Nothing is padding and the key scoping facts come first.

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, no-output-schema list tool with fully documented optional parameters, the description covers audience, ordering, defaults, and sibling routing — enough to call correctly. The only gap is the slightly imprecise description of the default date window.

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 100%, so all four parameters are already documented in the schema itself. The description adds the ordering semantics around the status filter and the default window, but its 'default: next 7 days' gloss is slightly at odds with the schema's from=24 hours ago / to=seven days from now pair, so it does not add clean value above baseline.

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 bookings', 'check booking requests') plus scope: pending requests first, then bookings in a period, with client contacts. It explicitly distinguishes itself from owner_decide_booking and owner_get_schedule, so an agent can pick it without opening sibling schemas.

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?

Gives explicit routing: use it to find requests to answer (then call owner_decide_booking) or to see who is coming; for a calendar view by staff or room use owner_get_schedule. The alternative and the condition that selects it are both named.

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