Booking requests waiting

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the 'from today on' starting boundary but says nothing about the local cache implied by the `fresh` parameter or whether results can be stale – useful mutation/staleness context is left implicit.

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?

A single short sentence with the scope front-loaded and no filler. Slightly held back by the noun-phrase form, which makes the action ('list these') implicit rather than stated.

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 list tool with full schema coverage and annotations, most of what an agent needs to call it is present. Without an output schema, however, the description gives no hint of what a 'request' contains (customer, service, requested time), which would help an agent decide appropriateness.

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 both `fresh` and `days_ahead` are documented in the schema itself. The description's 'from today on' only loosely relates to `days_ahead` and does not clarify the default 31-day window, so it adds nothing beyond the schema 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?

The description identifies the resource precisely (appointments awaiting salon confirmation or decline) and the temporal scope (from today on), which is more specific than the title alone. It stops short of a verb-based statement like 'list' and doesn't name a distinguishing sibling such as appointment_changes_feed or calendar_agenda.

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?

'Appointments that wait for the salon to confirm or decline' implicitly signals the use case (reviewing pending booking requests), and 'from today on' scopes it. There is no explicit when-to-use/when-not-to-use statement and no named alternative for getting accepted or past appointments.

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