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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: it requires manager-level access, needs a Cotlet API key with app access, and returns a CSV download link containing booking IDs for reconciliation.

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 key information (CSV export, download link) is front-loaded, but 'Manager users only' is stated twice and the opening clause partly duplicates the tool name and title. It is readable but has clear redundancy that costs it a point.

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 export with no output schema, the description covers the essentials: the output artifact (CSV download link), its contents (booking IDs matching Hostelworld references), the required date range, and the access prerequisites. Only a note on rate limits or link expiry is missing.

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% and both parameters are documented as Start/End date in the schema. The description only restates 'for a date range', adding no format or boundary details beyond the schema, so the baseline of 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 (exports guest payments as a CSV download link) and names the reconciliation use case. An agent can tell this apart from list_payouts or list_bookings by the export/CSV framing, though it does not explicitly name a sibling alternative.

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?

Provides permission gating ('Manager users only') and requires a date range, which is useful preconditions context. However, it never states when to choose this over sibling tools like hostelworld_list_payouts, nor any exclusions or alternatives.

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