List payment links

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description adds nothing beyond the schema: no pagination behavior, no default page size, no ordering or cursor semantics, and no hint about what the collection response looks like.

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?

'List payment links.' appears twice, once as a standalone line and once opening the second sentence, so roughly half the text is verbatim duplication. What remains is front-loaded and short, but the waste is disproportionate for a two-sentence description.

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?

The tool has five optional parameters including a nested created date object, and no output schema, yet the description says nothing about pagination, defaults, or result shape. For a list endpoint whose main invocation risk is unbounded or mis-paged retrieval, this leaves key behavior undocumented.

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%, including per-field docs for limit, status, the nested created time filters and both cursors, so the baseline is 3. The description only restates the status filter that the enum already documents and adds no meaning to limit or the cursor parameters.

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 payment links'), which cleanly separates it from get_payment_link, create_payment_link and update_payment_link in the sibling set. It loses a point because it offers no scope or differentiation statement beyond the verb, and it simply repeats the title.

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?

There is no when-to-use or when-not-to-use guidance at all. The only directive is that a status filter exists, which is already declared by the schema enum, so an agent gets no routing or exclusion logic from the description.

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