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

With only readOnlyHint available in annotations, the description carries useful extra burden: it discloses paging behavior (default 100/page), where the page count lives (request.pages), and the exact shape of a returned row. It does not discuss rate limits or ordering semantics beyond the ambiguous 'newest filters first'.

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 dense sentences with the resource and filters front-loaded and no filler. The only drag is the unclear 'newest filters first' clause, which reads ambiguously and slightly muddies the opening line.

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 an 11-param, zero-required, all-optional list tool, the description covers filtering, row shape, and pagination well. The absence of an output schema means the row-field enumeration is genuinely needed context, though page/limit interaction and default ordering could be spelled out more precisely.

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 the 11 parameters — including the '<'/'>' date prefix syntax — are already fully documented in the schema. The description only restates which filters exist, adding no syntax or default detail beyond what structured data provides, 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?

Names a specific verb+resource ('List bookings') and enumerates the filter dimensions (status, customer, dates, item, partner) plus the fields each row returns, so the agent knows exactly what the call produces. It does not explicitly differentiate from the sibling `checkfront_get_booking`, though the singular/plural naming makes the distinction inferable.

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 filter enumeration implies when the tool is useful (broad retrieval narrowed by status/customer/date/item/partner), but the opening phrase 'newest filters first' is garbled and there is no explicit when-to-use vs. alternatives or exclusion guidance. Usage is implied rather than stated.

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