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

Annotations already declare readOnlyHint and idempotentHint true, so the description is not responsible for safety. It adds behavioral context: results are bounded/paginated, only active catalog items are included, and guest charges, folio data, display colors, and credentials are omitted. This exceeds what annotations convey.

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?

Single sentence that front-loads the action and resource, then appends the key exclusions. Every clause adds information and there is no redundant restatement of the title.

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 a full output schema and strong safety annotations, the key missing piece is parameter guidance, especially hotelId. The description covers purpose, scope, and exclusions well, so overall context is adequate though not perfect.

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 0% and there are no property descriptions, so the description must compensate. It implies pagination via 'bounded page' but never explains limit, offset, or hotelId, and hotelId is a meaningful filter absent from the prose. Agents would need to rely on names and constraints.

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?

Description identifies a specific verb ('List'), resource ('active add-on / extra-service catalog'), and scope ('authenticated organization', 'bounded page'). It also names exclusions, which helps disambiguate from other catalog/hotel tools. This clearly differentiates it from siblings focused on hotels, rooms, rates, and availability.

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 clear context that this is for the extras/service catalog and notes that it returns only active, bounded results. It does not name alternative tools or explicitly state when not to use it, but the sibling set has no overlapping extras tool, so the context is sufficient. The exclusions of guest charges, folio data, colors, and credentials further warn about scope.

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