Appointment payment

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not disclose that results may be cached (relevant because the `fresh` parameter exists), nor what the returned 'state' consists of.

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 short sentence with no filler, front-loaded with the resource content. It is efficient, though the brevity comes at the cost of specificity rather than being a model of informative concision.

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?

This is a simple one-appointment read with full annotation coverage and complete schema descriptions, which lowers the burden. But with no output schema, the description should say more about the shape of the returned payment state and its relationship to sibling payment tools; it only lists field categories.

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 100%, so both parameters (appointmentId and fresh) are already documented in the schema. The description adds no extra meaning about the appointmentId source or the cache-bypass tradeoff, so the baseline 3 applies.

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 names the specific data returned (deposit, payment, tip, refund) and scopes it to a single appointment, which is more informative than a tautology. However, it is a bare noun phrase with no verb, and it does not distinguish itself from close siblings such as appointment_details or payment_rows, leaving the agent to infer the difference.

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?

There is no guidance on when to use this tool versus appointment_details, payment_rows, or booking_charges. No prerequisites, exclusions, or selection criteria are stated.

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