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

Beyond the readOnlyHint annotation, the description adds useful behavioral context: results are sorted by date (nearest first), each booking includes a status field to distinguish active vs cancelled, and requiring authorization. It does not mention pagination or error cases, but the annotation already conveys read-only safety, lowering the bar.

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 three sentences long, front-loaded with the core purpose, and every sentence adds value: purpose/ordering, status field semantics, and parameter default. No redundant or filler content is present.

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 low-complexity tool with one optional parameter and a read-only annotation, the description covers purpose, ordering, status, default parameter behavior, and authorization. It does not explicitly state the return format, but with no output schema expected, the provided detail is sufficient for effective 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?

The schema defines only provider_id with no description, so the description carries the burden of explaining it. It does so by noting the parameter is optional and that omitting it defaults to the first venue, which adds meaningful usage context beyond the bare schema.

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 the tool lists the user's current/upcoming bookings at a network venue, ordering by date nearest first. It implicitly distinguishes from sibling list_past_bookings by specifying 'current/upcoming' rather than past, making the purpose 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?

The description provides clear context for when to use this tool (to view active/upcoming bookings) and mentions the optional provider_id behavior. It does not explicitly state when not to use it or name alternatives, but the distinction from list_past_bookings is implied through the 'current/upcoming' wording.

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