list_fees

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

No annotations are present, so the description carries the full burden. It only says 'List', implying read-only, but fails to disclose details like pagination behavior (max_items), ordering, required permissions, or the effect of null booking_id. This is a minimal description that adds little beyond the obvious fact that it retrieves fees.

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?

A single, front-loaded sentence that captures the core action and the key optional filter. There is no redundant wording, and every element is purposeful.

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?

As a simple listing tool with two optional parameters and an output schema, the description covers the essential purpose, but it omits any explanation of max_items and provides no behavioral context (e.g., ordering, authentication, or null behavior). The output schema likely handles return structure, but the description still leaves the agent with unaddressed questions.

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?

With 0% schema description coverage, the description must explain all parameters. It implicitly covers booking_id via 'optionally for a single booking', but says nothing about max_items, leaving that parameter undocumented. The description does not compensate for the schema gap.

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 ('List'), a clear resource ('booking fees'), and an optional filter ('optionally for a single booking') that distinguishes it from siblings like list_bookings or list_payments. It leaves no ambiguity about the tool's core function.

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 context clue that fees can be scoped to a single booking via booking_id, but it does not mention alternatives or specify when to choose this tool over related siblings (e.g., list_payments, list_quotes). The agent must infer selection from the resource name alone.

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