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

With only readOnlyHint in the annotations, the description carries the behavioral load and does so well: it discloses pagination behavior (default 100/page, request.pages for page count) and enumerates the exact fields returned in each row (booking code, status, totals, customer name/email, summary, date_desc). This is valuable context beyond the annotations.

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 tightly written sentences: purpose and filters first, return fields second, pagination and API endpoint third. Every sentence adds distinct information with zero waste, and the most important details are front-loaded.

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 list tool with 11 fully documented parameters, no output schema, and a readOnly annotation, the description supplies the missing return-field and pagination context. An agent has everything needed to call it correctly and interpret the response structure.

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 schema already documents every parameter precisely. The description groups filters into categories ('by status, customer, dates, item or partner') but adds no syntax, format, or constraint details beyond what the schema provides. Baseline 3 is 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?

The description states a specific verb and resource ('List bookings') and enumerates supported filters, making the tool's core operation immediately clear. However, it does not explicitly distinguish this list endpoint from siblings like checkfront_get_booking or checkfront_search_customers, leaving that differentiation to the tool name alone.

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 description lists available filters but provides no guidance on when to use this tool versus alternatives such as checkfront_get_booking for a single booking or checkfront_search_customers. No exclusions, prerequisites, or contextual triggers are offered.

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