get_booking_payments

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

With no annotations, the description carries full burden. It indicates the tool returns payment breakdown with methods, amounts, and detection source, but does not disclose permissions needed, error behavior (e.g., booking not found), or side effects. For a simple read operation, this is adequate but not thorough.

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?

The description is very concise: two sentences specifying purpose and parameter, with a structured Args and Returns section. No irrelevant information, and the key points are front-loaded.

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?

Given the low complexity (one param, no output schema), the description covers the essential aspects: what it does, what parameter is required, and what is returned (payment breakdown including methods, amounts, and detection). It is complete enough for a simple read tool, though the return structure could be slightly more detailed.

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 coverage is 0%, so the description compensates by explaining 'booking_number' as 'The Bookeo booking number'. This adds clear meaning beyond the schema's generic title. For a single required parameter, it is sufficient.

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 clearly states the verb 'Get' and the resource 'payment details for a specific booking'. It differentiates from sibling tools like get_booking (returns booking info) and search_bookings (returns list of bookings) by focusing exclusively on payments.

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 provides the required parameter (booking_number) but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or when-not-to-use information is given, leaving the agent to infer based on the specific payment focus.

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