Get items report

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description adds genuinely useful provenance context: the endpoint and parameters were 'inferred from the SingleOps web app's own traffic; confirm results.' That is a meaningful reliability caveat an agent should know. It stops short of describing pagination defaults, auth needs, or rate limits.

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?

After a front-loaded purpose sentence, the description devolves into a ~60-item verbatim dump of parameter names that duplicates the input schema, making it hard to scan. The trailing return-key list is somewhat useful but the body is largely redundant bulk.

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 79-parameter tool with no output schema, the description does supply the return keys (draw, recordsTotal, recordsFiltered, data, meta, table_id, settings), which fills the output-schema gap partially. But it never explains what the report's data rows contain or how the ten column groupings map to real fields, leaving the agent under-informed about result interpretation.

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 schema already documents every parameter, and the description's long enumeration of query params merely repeats those names with zero added meaning (no formats, defaults, or interactions). Baseline 3 applies since the schema carries the semantic load.

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 first sentence plus the GET path make the verb and resource explicit: this fetches the items report. However, it never says what an 'items report' actually contains or how it differs from close siblings like get_item_groups_report, get_master_line_item_report, or list_items, so the agent cannot disambiguate on purpose alone.

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?

There is no statement of when to call this instead of the many neighboring report tools, nor any prerequisite or exclusion. The only guidance-ish text is 'confirm results,' which cautions about reliability but does not route the agent among alternatives.

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