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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally. The description reinforces read-only scope ('this server never issues refunds') and adds the endpoint, but nothing about the return shape, pagination, or behavior on an unknown id. The 'POST' mention alongside a read-only operation is transport detail, not a contradiction of the annotations.

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?

Very short and front-loaded, with no filler sentences. It is slightly telegraphic (parenthetical plus a bare endpoint path), but every clause carries information.

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 would ideally say what 'in full' returns or how a missing id is handled. It gives a hint ('in full') and the annotations cover safety, so the gap is moderate rather than severe.

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 both parameters are documented there, including the include_contact default behavior. The description only echoes 'by id' for refund_id and adds nothing about include_contact, so baseline 3 applies when the schema carries the load.

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+scope: fetch one refund in full by its id. This implicitly differentiates it from the sibling list tools (qgiv_list_recent_refunds, qgiv_list_refunds_by_date), but never names them explicitly, so the contrast is inferable rather than stated.

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 clarifies a when-not ('this server never issues refunds'), which prevents an agent from attempting a write. However, it does not say when to prefer this over qgiv_list_refunds_by_date or qgiv_list_recent_refunds; the selection logic is only implied by 'one ... by id'.

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