get_guests

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that by enumerating the returned payload (profiles, points balance, booking history, timestamps) in the absence of an output schema. It omits pagination/volume behavior, which keeps it from 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?

Structure is clear and front-loaded, but it is padded for a zero-parameter list tool: the 'Quick Start' section restates what the Overview already said ('Returns all guests with their loyalty program details'), and the returned-field list is repeated in prose. Content is well organized but redundant.

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 simple no-param read tool with no output schema, the description covers the call contract and describes return contents in enough detail for an agent to use the result. Missing volume/pagination expectations is the only notable gap.

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?

There are zero parameters, so the baseline is 4. The description correctly states 'No parameters required,' which matches the empty schema and removes any ambiguity about whether filtering is possible.

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 states a specific verb and resource ('Retrieve a complete list of all guests enrolled in your loyalty program') and scopes it with 'all guests', which implicitly distinguishes it from the singular get_guests_guestid sibling. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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?

A dedicated 'When to Use' section lists four concrete scenarios (guest management, points administration, customer support, reporting), giving clear context for invocation. It provides no exclusions or explicit alternatives, so it stops short of a 5.

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