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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: 10-per-page limits, cursor-based pagination (not page numbers), and the two distinct cursor param sets for filtered vs unfiltered reads.

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?

Front-loads the core purpose, then layers endpoint/pagination detail in a compact block. Dense but every sentence carries operational meaning; only slightly crowded with endpoint notation.

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?

With no output schema, the description closes the gap by stating it 'Returns a JSON array of bookings' and explains both pagination schemes. Complete enough to call correctly; the only minor gap is not covering the fields parameter behavior explicitly.

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 the baseline is 3, but the description adds cross-parameter meaning the schema lacks: after is required for filtered reads, maxResults is 10-500, and params carries direction/boundaryStartsAt/boundaryId or fromBookingId depending on mode.

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 on your account') and draws a clear line between unfiltered and filtered reads. It does not explicitly differentiate from siblings like get_booking or list_profiles, so it stops short of a 5.

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 conditions selecting the unfiltered read (GET /v1/{accountId}/bookings) versus the filtered query ('supply after as the required start of the time range'). Clear context for choosing between the two modes, though it never mentions when to prefer get_booking for a single record.

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