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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real value by pre-empting a likely agent error: it states plainly that no payment is taken by the server, which no annotation conveys. It does not discuss freshness of the scraped site data or pagination, but for a zero-param lookup that is minor.

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?

It is a single sentence with no filler, and the core noun phrase 'Every way to pay at TF Handy Wash' is front-loaded. The structure is a long comma-and-parenthetical chain, which is dense to parse, but each clause maps to a distinct piece of returned content rather than repeating structured fields.

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?

An output schema exists, so the description does not need to document return shape, and it does not try. What an agent needs in order to select this tool correctly, namely the breadth of payment content covered and the fact that payment itself happens on site, is fully stated for a zero-param read tool.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter guidance, since there is nothing to parameterize, and instead spends its words on return content.

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 resource (payment methods at TF Handy Wash) and enumerates exactly what is returned: accepted tender types, the Speed Queen app block with location code HANDYW, change-machine and surcharge lines, and paying FAQ answers. It is clearly distinct from siblings like get_pricing or get_amenities by content, though it never names those siblings explicitly.

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 scope is unambiguous: this is the tool for 'how do I pay' questions, and the closing clause 'Payment happens at the machine; this server takes none' tells the agent this cannot initiate or process a payment. There is no explicit when-not or named-alternative routing, which keeps it short of a 5.

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