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

Annotations already establish readOnlyHint=true, so the safety profile is covered; the description adds real behavioral context beyond that: the default date window, the meaning of author account id (0 = customer), the private flag, and the underlying API route. It omits pagination/result-limit behavior, which is the main remaining gap.

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?

One dense sentence carries scope, default, and return shape, with the endpoint appended as a compact reference. Nothing is padded and the most decision-relevant facts come first.

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 compensates by enumerating returned fields (booking code, author id, date, body, private flag) and the default time window, so an agent knows what it will get. Only result volume/pagination behavior is left unspecified for what is otherwise a simple single-param list tool.

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% on the single date parameter, so the baseline is 3, but the description adds the default-window semantics that the schema does not express. That extra meaning justifies a 4 rather than a flat baseline.

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 ('List the notes left on bookings across the account') and enumerates the returned fields, which cleanly separates it from the write-side sibling checkfront_add_booking_note. An agent can identify the operation without opening the schema.

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?

Discloses the default scope ('default: the past 30 days'), which tells the agent what happens if it omits the date parameter. There is no explicit statement of when to prefer this over an alternative or how to get an unbounded window, so it stops short of a full when/when-not rule.

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