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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data window (last 30 days), the source constraint (customer payments on the user's own site via Stripe), and the fact that it hands back a one-time Stripe dashboard link rather than only aggregate numbers.

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?

Front-loaded with the resource and its scope, followed by the routing sentence. The middle inventory of returned fields is dense but each item earns its place by describing the payload. It is a single long clause-stacked sentence, which slightly hurts scanability but not comprehension.

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?

With no output schema, the description carries the full burden of describing returns and does so: totals, 30-day window, fees, latest payments with receipt links, and a Stripe dashboard link. Combined with the sibling routing and the read-only annotation profile, an agent has everything needed to call and interpret this correctly.

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, which is the baseline-4 case; there is no parameter syntax or semantics an agent could get wrong. The description correctly implies a no-argument summary call rather than a filtered query, so nothing is misleading.

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?

States a specific verb/resource and scope: payments customers made for bookings on the user's own website, and enumerates the payload (totals, last 30 days, fees, latest payments with receipt links, Stripe dashboard link). It explicitly distinguishes itself from the nearest sibling, get_billing_status, so an agent can route correctly without opening either schema.

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?

Gives explicit triggers ('Use when the user asks about payments, receipts, payouts, revenue from bookings, or their Stripe account') and an explicit exclusion with the alternative named ('Not their oriiion subscription — that is get_billing_status'). Both when-to-use and when-not-to-use are covered.

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