list_online_payments

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention return format, pagination, sorting, authentication, or any side effects. The noun phrase provides no insight into how the tool behaves beyond the basic subject matter.

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 extremely brief (a single phrase), which is concise, but it lacks proper sentence structure and front-loading. It under-specifies rather than earning its place with informative content.

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 no annotations, no output schema, and minimal schema info, the description should compensate. It fails to explain what the tool returns, what status values exist, or how limit behaves. The description is grossly incomplete for a tool with two parameters and no other documentation.

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 schema defines two parameters (limit, status) with no descriptions and schema description coverage is 0%. The description does not mention these parameters at all, leaving their meaning and usage completely undocumented.

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 is a noun phrase 'Paiements en ligne reçus (Stripe/PayPal)' which identifies the resource as received online payments from Stripe/PayPal. It adds context beyond the tool name, distinguishing it from broader payment tools like list_payments, but lacks an explicit verb or statement of what the tool does (e.g., 'Lists...').

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 list_payments or list_supplier_payments. The mention of 'online' and 'Stripe/PayPal' implicitly suggests a specific subset, but there is no explicit context or exclusions.

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