list_payments

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

With no annotations present, the description must disclose behavioral traits. It does not state whether this operation is read-only, destructive, or has any side effects. It also fails to mention pagination behavior beyond parameter defaults, which are already in the schema. The description adds no behavioral clarity.

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, concise sentence: 'List payments with optional filters.' It is front-loaded with the action and resource, containing no wasted words. Every part earns its place.

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?

Given the lack of annotations and output schema, the description is insufficient. It does not explain the return format, error conditions, or any special behavior (e.g., maximum results, ordering). For a list operation, more detail is expected to ensure correct usage.

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 description mentions 'optional filters,' which is a generic reference to the parameters. Since schema coverage is 100% and all parameters (per_page, page, client_id) have descriptions, the description adds little meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'List payments' which uses a specific verb and resource. It also mentions optional filters. However, it does not distinguish this tool from sibling list tools like list_clients or list_invoices, but the resource name 'payments' is unique enough to convey the purpose.

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 guidance is provided on when to use this tool versus alternatives, such as get_payment for a single payment or other list tools. There are no prerequisites, exclusions, or context for when filters are appropriate. The description lacks any usage direction.

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