Get item groups report

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a meaningful caveat that the endpoint was inferred from observed traffic and results should be confirmed — useful context beyond annotations — but it says nothing about pagination, rate limits, or result shape beyond listing keys.

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 purpose and caveat are front-loaded, which is good, but the description then dumps a massive 55-item parameter list that merely duplicates the schema keys, bloating the text without adding information. That enumeration does not earn its space.

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 55-parameter report tool with no output schema, the description does list the return keys (draw, recordsTotal, recordsFiltered, data, meta, table_id, settings), which partially substitutes for an output schema. But it leaves the meaning of the many filter/column parameters and the actual report content unexplained, so an agent cannot construct a meaningful call beyond guessing.

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 nominally 100%, but every property description is a tautology ('Query parameter "draw".'), so the schema provides no real semantic value. The description only enumerates parameter names with no explanation of meaning, format, or which are important, leaving effective semantic coverage low despite the reported number.

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?

States a specific verb and resource ('Get item groups report') and cites the underlying endpoint GET /reports/item_groups_report. However, it does not distinguish this report from close siblings like singleops_read_list_item_groups or singleops_read_get_items_report, so an agent cannot easily tell which one applies from the text 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 explicit when-to-use, when-not-to-use, or alternative recommendation. The only caveat is 'Inferred from the SingleOps web app's own traffic; confirm results,' which is a reliability warning rather than routing guidance.

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