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

The readOnlyHint annotation already covers side-effect safety. The description adds context about platform verification and transaction hashes, but does not disclose pagination behavior or result ordering. This is acceptable but not rich.

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?

One sentence conveys the resource, scope, and a key output attribute with no filler. It is front-loaded with the most important noun phrase and earns every word.

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 no output schema, the description states what is returned but not how pagination works or how this tool relates to siblings like payment_info and job_receipt. It is minimally viable but has notable gaps.

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 0% and the description never mentions the limit or cursor parameters. For low coverage, the description needed to compensate by explaining pagination semantics, but it does not, leaving cursor behavior unexplained.

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?

The description clearly identifies the resource: 'payments and refunds the platform verified for my jobs', and adds an output detail ('with transaction hashes'). It does not explicitly differentiate itself from siblings like payment_info or job_receipt, so it is clear but not fully distinguishing.

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?

The phrase 'for my jobs' gives a clear scope for when this tool applies, and 'verified' communicates a meaningful filter. It does not mention alternatives or exclusions, but the usage context is reasonably clear from the description alone.

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