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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the full safety profile is covered. "Effects: None." merely restates those structured hints and earns no credit, though the note that availability is scoped to "this connection" adds a small useful nuance.

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 compact sentences: contents first, the imperative "Call this first" second, no filler. Every clause carries information and the critical routing instruction is not buried.

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 takes on the job of describing the payload and does enumerate what comes back, which is the key thing an agent needs. It stops short of describing the response shape (list vs. nested object) or field naming, so a small gap remains.

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?

The tool takes zero parameters, so the baseline of 4 applies and there is nothing for the description to compensate for. The schema coverage figure is nominal given an empty properties object.

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?

Specific verb ("Lists") plus a precisely scoped resource, with the returned contents enumerated (products, party and room limits, cabins, booking modes, available tools). No sibling tool does discovery, so it is instantly distinguishable from the 17 lookup/quote/booking 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?

"Call this first." is an explicit, unambiguous ordering directive that tells the agent when to use it relative to every sibling. There are no when-not conditions or named alternatives, but for a unique zero-arg discovery tool that omission is minor.

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