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

Annotations only carry readOnlyHint=true, so the description has to add real behavior and it does: an OAuth scope requirement (bookings-financial) and an Alpha stability caveat, both of which materially affect whether and how the agent calls it. It stops short of describing pagination behavior or the response envelope, but that is a reasonable omission.

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?

Three short sentences, each doing distinct work: what is returned, the auth/lifecycle constraints, and the underlying REST endpoint for traceability. Purpose is front-loaded and there is no filler or repetition.

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 adequately conveys the return shape (invoices plus charge and payment line items) and the access requirement. The only gap is pagination/response-envelope behavior, though the 'page' parameter's own description already points at pages.nextPageExists.

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% - both 'page' (with nextPageExists guidance) and 'bookingIds' are fully documented in the schema. The description only implies a booking-scoped listing ('for bookings') and adds no syntax, batched-limit, or paging meaning beyond what the schema already states, so baseline 3 applies.

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?

Specific verb (List) plus resource (invoices) and it goes further by naming the sub-resource returned: line items (charges and payments) for bookings. That is more precise than a bare 'list invoices'. It does not explicitly contrast itself with any sibling tool (e.g. beds24_list_bookings), though no sibling covers invoices, so the risk of mis-selection is low.

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?

It supplies two real preconditions - the bookings-financial scope and the fact that Beds24 flags the endpoint as Alpha - which tell an agent when the call will succeed and how much to trust it. However, there is no statement of when to reach for this tool versus producing invoice data another way, nor any exclusion. Usage is implied rather than prescribed.

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