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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds what fields come back (name, price, currency, configuration) and the underlying GET endpoint. It does not discuss pagination behavior (limit/offset + next_offset) or rate limits, which would have made it 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?

Front-loads the identity and disambiguation in the first sentence, then adds the retrieval fields and modes, ending with the endpoint. Every sentence carries unique information and there is no filler.

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?

There is no output schema, and the description compensates by naming the returned fields (name, price, currency, configuration) plus the endpoint. The only gap is the undocumented search_term parameter and any note on paging behavior, which the schema partially covers via next_offset.

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 80% and the schema already documents limit, offset, product_id and appointment_id in detail. The description only restates the product-filter and single-fetch modes and says nothing about the undocumented search_term parameter, so it adds little beyond the schema. 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?

Names a specific verb and resource ('List appointments') and immediately disambiguates the overloaded term by defining appointments as bookable services/variants, while naming what they are not. The agent can distinguish it from appointo_list_bookings without opening either 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?

Explicitly states the exclusion ('not the bookings themselves') and routes to appointo_list_bookings for those, and describes the two access modes: filter by product, or fetch one by id. Alternatives are named with the condition that selects them.

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