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

readOnlyHint=true already tells the agent this is a safe read, and the description only restates the HTTP endpoint (GET /v1/refunds/), adding no behavioral context such as pagination behavior, result ordering, or what happens when the token spans multiple organizations (the organization_id note lives only in the schema). Nothing contradicts the annotations, but nothing is added either.

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 short clauses, front-loaded with the purpose before the endpoint reference. The trailing 'Polar: GET /v1/refunds/.' is mostly filler but costs little.

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?

For a read-only paginated list tool with full schema coverage and readOnlyHint annotations, the description is nearly sufficient. It omits any hint of the returned refund shape, which matters slightly more here because there is no output schema, but an agent can still invoke it 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 description coverage is 100%, so the six parameters are already fully documented in the schema and the baseline is 3. The description adds no format or syntax detail beyond the schema, and its 'subscription' filter mention does not correspond to any parameter.

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 and resource ('List refunds') plus the filter dimensions, so it is clearly distinguishable from the other polar_list_* siblings that cover different resources. Minor flaw: it advertises filtering by 'subscription', but no subscription parameter exists in the 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?

No when-to-use guidance, no exclusions, and no routing to alternatives such as polar_create_refund or polar_get_order for the filter ids. The filter list implies how to narrow results but never says when this tool is the right choice versus the single-refund or order tools.

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