merit_list_sales_offers

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

No annotations are present, so the description carries the full burden. It does disclose the endpoint and detailed filter semantics (DocType, DocStatus), which is useful. However, it never explicitly states that the operation is read-only or describes the response shape, and naming a POST endpoint without safety clarification leaves some ambiguity.

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 compact single paragraph that front-loads the purpose and then enumerates parameter semantics without fluff. It could be improved with line breaks or bullets for readability, but every clause carries meaningful information.

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 list operation with no output schema, the description omits the return payload structure, pagination, or any sample response. It also introduces DocType/DocStatus parameters not present in the schema without clarifying whether they are optional or how to pass them. An agent is left guessing about essential call results.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by introducing DocType and DocStatus enums that are absent from the input schema, and it reinforces the 3-month period constraint. This goes beyond what the schema alone provides.

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 a clear verb-resource pair ('List Merit Aktiva sales offers') and names the underlying endpoint (POST /api/v2/getoffers), making the operation unmistakable. The plural 'offers' also distinguishes it from the sibling merit_get_sales_offer, which fetches a single offer.

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?

The description provides parameter constraints and enum meanings, but no explicit guidance on when to choose this tool over alternatives like merit_get_sales_offer or merit_list_sales_invoices. Usage is implied by the verb 'List' and the resource name, but there are no when-to-use or when-not-to-use criteria.

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