list_payments_for_date_range

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the basic operation (list payments by date range) without mentioning side effects, authentication requirements, rate limits, pagination, sorting order, behavior on invalid dates, or handling of the optional 'top' parameter. Critical behavioral traits are omitted.

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, focused sentence that conveys the core purpose efficiently. It is not verbose, but the brevity sacrifices important details that could be included without damaging conciseness.

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 tool has 3 parameters (2 required), no annotations, and an output schema, the description fails to fully equip an agent to use it correctly. It omits explanation of the 'top' parameter and does not clarify the date range behavior. While the output schema exists, the input side is under-specified.

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 has 0% description coverage. The description adds format guidance for 'start_date' and 'end_date' (YYYY-MM-DD) but does not explain their semantics (inclusive/exclusive) or the meaning, default, or effect of the optional 'top' parameter. This leaves significant ambiguity for correct invocation.

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 the verb 'list', resource 'payments', and constraint 'within a date range', with date format specified. It clearly distinguishes from sibling tools like 'list_payments' (unfiltered) and other filtered 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 explicit guidance on when to use this tool versus alternatives such as 'list_payments', 'list_payments_for_client', or 'list_payments_for_project'. The context is implied by the name and date-range parameters, but no direct comparison or exclusion criteria are provided.

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