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

With readOnlyHint=true already covering the safety profile, the description adds real value: a required scope for authorization, an upstream maturity warning ('Beds24 marks this endpoint Alpha'), and the backing REST endpoint GET /bookings/invoices. It does not mention pagination behavior, though the schema covers that.

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 carrying a distinct fact (what is returned, the auth scope, the stability signal and upstream route). Purpose is front-loaded and there is no filler.

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 two-parameter, read-only list tool with no output schema, the description covers what is returned (invoices plus line items) and the auth requirement, which is the essential missing structured context. Pagination and filtering semantics live in the schema, so nothing essential is absent, though a note on result volume or pagination expectations would round it out.

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 both bookingIds and page are already documented with usage hints (the page description even points at pages.nextPageExists). The description adds no parameter-level detail beyond the schema, so the 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?

States a specific verb and resource ('List invoices and their line items') with the scope narrowed to bookings, and even names the payload contents (charges and payments). It clearly separates the invoices resource from the sibling bookings-list tools, but it never explicitly differentiates itself from any named sibling.

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 only guidance is a prerequisite, 'Requires the bookings-financial scope,' which is useful but is an auth requirement rather than a when-to-use statement. There is no statement of when this is preferable to beds24_list_bookings or beds24_get_booking, so usage is only implied by the resource name.

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