list_payments

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

No annotations provided. The description does not disclose any behavioral traits such as whether this is a read-only operation, pagination behavior, or rate limits. It simply says 'List payments', which is insufficient for a mutation-unaware agent.

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 very short (one sentence), which aids conciseness, but it omits critical information. It is not front-loaded with the most important details like what the tool returns or how to use parameters beyond filter_expr.

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 presence of an output schema and many sibling tools, the description fails to explain the scope of 'payments' listed (all? within a project?). It lacks completeness for an agent to confidently invoke this tool without risking incorrect filtering.

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?

With 0% schema description coverage, the description must compensate. It only mentions filter_expr, ignoring top, skip, select, orderby. It does not explain their semantics or default behaviors, leaving the agent to guess.

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 states 'List payments' which identifies the action and resource, but it is too generic among many sibling tools like list_payments_for_client, list_payments_for_date_range, etc. It does not specify the scope or filtering defaults, making it hard to distinguish.

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 on when to use this tool versus other payment listing tools. The only mention is 'use filter_expr for OData filtering', but no context about prerequisites or when not to use this tool.

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