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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still adds the required auth scope and names the underlying GET /properties endpoint. It stops short of describing pagination behaviour, which the agent must infer from the page parameter.

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 tight sentences: what is listed and returned, then optional flags, then the auth requirement and endpoint. The highest-value information is front-loaded with 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?

With 11 optional params and no output schema, the description usefully pre-announces the returned fields and the scope requirement. It leaves paging and id-filtering semantics to the schema, which is a minor gap rather than an omission that would cause a wrong call.

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 73% and the schema documents page, roomIds/propertyIds and the include flags individually. The description categorises five optional include flags (texts, pictures, offers, unit details, all rooms) but says nothing about page, roomIds, propertyIds, includeLanguages, includePriceRules or includeUpsellItems — a baseline 3 with modest added framing.

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 (properties in the account) and enumerates the payload returned — address, currency, check-in times, room types. No sibling covers property listing, so an agent can distinguish it immediately from the booking/room/review tools.

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 gives a prerequisite ("Requires the properties scope") but no explicit when-to-use or when-not-to-use guidance, and no named alternative. Usage is implied by the resource name rather than stated.

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