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

The readOnlyHint annotation already establishes this is a safe, non-mutating read. The description adds the underlying REST endpoint (GET /v1/refunds/), which is mild extra context, but says nothing about pagination behavior, result ordering, or empty-result handling beyond what the schema's page/limit fields imply.

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 sentences with the purpose front-loaded and no filler. The trailing 'Polar: GET /v1/refunds/' is marginal but harmless.

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 lightly annotated list tool with a fully documented schema and no output schema, the description covers the essentials. It omits any hint of the response shape or pagination semantics, which an agent listing potentially large collections would benefit from knowing.

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 every parameter is already documented in the schema, giving a baseline of 3. The description paraphrases filters but adds no format or syntax detail, and its mention of 'subscription' does not map to any actual 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 (List) and resource (refunds), plus the filter dimensions. However, it names 'subscription' as a filter dimension while no subscription parameter exists in the schema, which slightly muddies the scope. Still clearly distinguishable from siblings like polar_create_refund or polar_list_orders.

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 statement of when to use this versus alternatives (e.g. polar_create_refund for issuing a refund) and no prerequisites noted. Usage is only implied by the verb 'List' and the listed filters.

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