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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds context beyond that: the shape of the returned data (charge ID, refund status) and the authorization requirement (a Cotlet API key with app access). It does not mention pagination or rate limits, but the auth note is genuinely additive.

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 what the resource is and what it returns, then the usage guidance and auth note. It is slightly redundant, restating 'payment processor charge ID and refund status' in consecutive sentences, but nothing is wasted materially.

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 correctly compensates by describing the returned fields, and it covers the auth prerequisite and the pre-refund usage flow. Minor gaps remain on error behavior and pagination, but an agent has enough to call 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?

Schema coverage is 100% and the single transaction_id parameter is already documented as coming from list_transactions. The description adds no syntax, format, or interpretation detail for the parameter, so the schema carries the burden and 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?

Specific verb (get) and resource (transaction), and it enumerates the returned fields: customer, offer, amount, charge ID, refund status. It contrasts a single transaction against the Transactions page listing and names refund_transaction, so the boundary with siblings is mostly clear, though the relationship to list_transactions is only implicit.

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?

It gives an explicit usage scenario: 'Use it before refund_transaction to check the amount and the customer,' which names the downstream alternative and the reason to call this tool first. It lacks any when-not guidance or other selection conditions, so it falls short of a full 5.

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