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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description carries a lighter burden. It adds useful value by naming the returned fields and the underlying REST route, but says nothing about failure modes (e.g., unknown id), auth scope, or response shape. Adequate but thin given the coverage it could add.

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?

Two sentences, zero filler, and the core purpose is front-loaded before the REST endpoint detail. Nothing redundant with the title or annotations.

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 usefully compensates by enumerating the returned content, and one required param plus a readOnly annotation is a simple surface. Only gap is error/not-found behavior, which is minor for a single-id lookup.

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% for the single 'id' parameter ('Charge id.'), so the schema already does the work. The description adds only 'by id' in prose, no format, bounds, or lookup hint beyond what the schema states — the correct baseline of 3.

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?

Specific verb + resource ('Get a single charge by id') plus an enumeration of the payload contents (line items, totals, status, scheduled date, customer/address). The word 'single' implicitly separates it from the sibling recharge_list_charges, so an agent can route without opening any 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?

Usage is implied by 'by id' — call it when you already hold a charge id — and by 'single' versus the list sibling. However, there is no explicit when-to-use/when-not statement, no mention of what to do if the id is unknown, and no named alternative. Minimum viable guidance.

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