Payment basket

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety is fully covered without the description. The only added context is the composition of the payload (deposit, payment and refund records); nothing is said about whether an unknown basketId errors or returns empty, nor about the effect of the documented cache on result freshness.

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?

One short sentence with no filler, which is appropriately sized in raw terms. But the terseness is partly under-specification rather than economy: the single fragment omits the verb and the lookup key, so brevity costs clarity instead of buying it.

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 two-parameter read with a fully documented schema, complete annotations, and no output schema, the description is close to sufficient. The gaps are the unstated operation verb and the unexplained relationship between the documented 'fresh' cache flag and the returned data, which an agent would want to know before calling.

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%: basketId has a pattern and 'fresh' documents the cache-skip flag, so the schema already carries parameter meaning. The description adds no format, scoping, or caching detail beyond that, which is the baseline case for a fully documented schema.

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 a specific resource and hints at its contents (deposit, payment and refund records), but it is a bare noun phrase with no verb, so the operation (fetch one basket by id) must be inferred from the name and schema. It also does nothing to distinguish itself from adjacent siblings such as payment_rows, payment_summary, checkout_transactions, or appointment_payment_details.

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 statement of when to use this tool, no prerequisites, and no mention of any alternative. With five or six payment-related siblings in the list, the absence of any routing guidance leaves the agent to guess based on name similarity alone.

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