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

Annotations already declare readOnlyHint=true, so the description gets credit for adding real context instead of repeating safety: the default look-back window, the returned field set, the private-flag disclosure, and the 0 = customer convention for author id. It omits pagination or result-count limits, keeping it just short of a 5.

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?

Two tight sentences with no filler; the scoping constraint (default 30 days) and output fields are front-loaded, and the raw endpoint is appended in a compact form.

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?

With no output schema, the description correctly compensates by naming what each returned note contains, and it pins down the default time window. It is nearly complete for a zero-required-parameter list tool, with only pagination/volume behavior unaddressed.

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%, so the baseline is 3, but the description adds semantics the schema lacks: the omitted-parameter behavior (defaults to the past 30 days). It still doesn't restate the accepted day/month formats, which the schema already covers.

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 (List) and resource (notes left on bookings) plus scope (across the account) and even enumerates the returned fields. An agent can immediately distinguish it from the sibling checkfront_add_booking_note, which writes rather than reads.

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 default window (past 30 days) is useful implicit usage context, but the description never states when to prefer this over checkfront_get_booking or checkfront_list_bookings, nor whether there is any way to scope it to a single booking. Usage is implied rather than guided.

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