list_paymentcards

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

With no annotations, the description carries the burden of disclosure. It explicitly states that only paymentcards created by the user are returned, which is a meaningful behavioral trait. However, it omits details about read-only safety, pagination, or error behavior, though these are less critical for a simple list operation.

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?

The description is a single, direct sentence that briefly states the tool's purpose without repetition or extraneous detail. It is appropriately front-loaded and concise.

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 zero-parameter read-only list tool with no output schema, the description adequately covers what the tool does and the filtering criterion (created by the user). It could mention return format or limits, but such details are not essential given the tool's simplicity.

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?

The input schema is empty with zero parameters, and the description implicitly confirms no inputs are needed. Per the rubric, zero-parameter tools receive a baseline of 4, and there is no additional parameter semantics to explain.

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 states the tool retrieves a list of paymentcards using the verb 'Get' and the resource 'paymentcards', adding 'paylinks' and 'created by the user' for ownership scope. This distinguishes it from sibling tools like create_paymentcard and other account list tools.

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 description provides no guidance on when to use this tool versus alternatives such as list_deposit_accounts or get_accounts_list. It does not specify any exclusions or preferred contexts, leaving usage decisions to the agent.

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