list_booking_requests

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. However, the description adds no behavioral context of its own, such as pagination behavior, status semantics, or open-world implications; it merely repeats the title.

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 short but under-specified: it repeats the tool name and does not earn its place by adding useful information. There is no front-loaded differentiation, filtering note, or behavioral detail; this is omission rather than true conciseness.

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?

The annotations cover read-only/idempotent behavior, all parameters are documented, and an output schema exists, so the invocation requirements are mostly satisfiable. The main missing pieces are business context and when-to-use guidance, which are addressed in the usage dimension; for a simple list endpoint this is minimally complete.

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 limit, offset, status, and subject_id are already documented. The description itself adds no parameter-level meaning, but with full schema coverage the baseline of 3 is appropriate and no compensation is needed.

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 'List Booking Requests' is a verb+resource phrase, but it exactly restates the tool name and title and adds no distinguishing scope or semantics. It also does not separate this from the many sibling list_* tools such as list_sessions or list_leads.

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 is provided on when to use this tool instead of alternatives. There is no mention of business context, prerequisites, or exclusions, so an agent has no basis for deciding between this and other list tools.

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