merit_get_purchase_report

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

No annotations are provided, so the description bears the full burden of behavior disclosure. It only reveals the HTTP method (POST) and the reportType codes; it does not state whether the call modifies data, whether it is safe to invoke repeatedly, what authentication or permissions are needed, or what the response looks like. This leaves significant behavioral uncertainty for a tool with zero annotation coverage.

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, front-loaded sentence that states the resource, the endpoint, and the core reportType mapping with no wasted words. The format is easy to scan and the most important identifying information appears first.

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?

The tool has no output schema and no annotations, yet the description does not explain return values, pagination, date-range semantics, or how the report content is structured. For a report tool, an agent would likely need more context about what the response contains and how it relates to other purchase-related tools. The description covers only the request mechanics and reportType meaning, leaving several practical gaps.

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 description coverage is 100%, so the baseline is 3. The description repeats the reportType enum meanings that are already in the schema and adds no new semantic detail about startDate or endDate beyond their format. It provides a small amount of redundancy but no substantive additional parameter clarification.

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 identifies a specific resource ('Purchase report') and the endpoint, and the reportType mapping distinguishes the four report flavors. The tool's name reinforces that it retrieves a purchase report, so an agent can tell it apart from sales-report siblings by the 'purchase' qualifier. It stops short of an explicit verb like 'retrieves' or 'generates', but it is not vague.

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 given on when to use this tool instead of closely related siblings such as merit_list_purchase_invoices, merit_get_purchase_invoice, or other report tools like merit_get_sales_report. There are no alternatives mentioned, no context about typical use cases, and no exclusions. The reportType mapping is a parameter explanation, not usage direction.

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