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

Annotations already declare readOnlyHint/openWorldHint/non-destructive, so safety is covered. The description adds real context beyond that: the auth requirement ('Cotlet API key with access to this app'), the newest-first ordering, and the important caveat that recent stays may be missing because payout follows checkout.

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?

Reasonably short and front-loaded, but the phrase 'each with the bookings it covers' duplicates the opening clause 'the bookings they cover'. One sentence is spent restating information already given, which is minor waste.

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 read-only list tool with one well-documented param, 100% schema coverage and no output schema, the definition supplies the return fields, ordering, auth prerequisite and the checkout-payout timing caveat. An agent has enough to call it correctly.

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% and the single 'since' parameter is fully documented in the schema, so the schema carries the burden. The description adds no syntax or format detail for it, making the baseline 3 appropriate.

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 ('Lists') and resource ('payouts') and enumerates the fields returned (amount, status, date, bookings covered) plus ordering (newest first). It doesn't explicitly differentiate from hipcamp_list_bookings by name, but the payout framing is clear enough.

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?

Implies usage via 'as the Payouts tab shows them' and the payout-after-checkout caveat, which tells an agent when this data is relevant. However, it never says when to prefer this over hipcamp_list_bookings or any alternative, and there are no explicit exclusions.

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