groups_reports_get_all

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

No annotations are provided, so the description carries the full behavioral burden. It only weakly signals read-only via a 'read-only' keyword, and says nothing about required permissions, pagination, response shape, or what report_type filtering does. Significant gaps for a list endpoint 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 useful content is two short clauses, swamped by a long redundant keyword list that repeats 'report/reports' and verbs dozens of times. The purpose is front-loaded, but the bulk of the text adds no value and dilutes signal.

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 endpoint with no output schema and no annotations, the description should explain what a report is, what report_type filters, and any scoping. Instead it stops at 'List reports', leaving the agent without enough context to use the filter correctly.

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 0% and the single parameter (report_type) with its ReportCategory enum (backup/restore/migration/bulk_import) is never mentioned in the description. The description fails to compensate for the coverage gap, leaving the optional filter undocumented.

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 clear verb and resource ('List reports', endpoint GET /api/groups/reports), which distinguishes it from the sibling groups_reports_get_one by the 'Get All' framing. The signal is somewhat buried under keyword spam, but the core purpose is unambiguous.

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 when-to-use or when-not-to-use text; the only guidance is the implicit 'Get All' vs the sibling 'get_one', which an agent can infer. No prerequisites or filtering conditions are stated.

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