merit_get_customer_payments_report

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

No annotations are provided, so the description carries the burden. It discloses automatic pagination following getmoredata, the required date range, and flags a wire typo (CurrncyCode). This is meaningful behavioral context beyond what the schema provides.

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?

Three sentences, each with a distinct purpose: identify the endpoint, describe pagination and automation, and state requirements plus a gotcha. No wasted words.

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 report tool with 100% schema coverage and no output schema, the description conveys the call surface, required inputs, pagination behavior, and a field-name quirk. It could mention the response structure, but that is not required given the absence of an output schema emphasizes the unknown return shape.

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 already describes all parameters with 100% coverage. The description adds value by clarifying the typo in the wire field name, emphasizing that periodStart/periodEnd are required, and noting the pagination parameter behavior. This is more than the schema alone would provide.

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 it is a customer payments report via a specific endpoint (POST /api/v2/getcustpaymrep), and distinguishes it through pagination behavior. The tool name itself is descriptive, and the description confirms the resource and action.

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?

It states the required parameters (periodStart/periodEnd) and describes pagination behavior explicitly (HasMore/Id4More, automatic getmoredata). It doesn't explicitly say when to choose this over sibling report tools, but the uniqueness of the endpoint and pagination note provide enough usage context.

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