List reports (snapshot data omitted)

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond restating the HTTP method — no pagination behavior, no ordering, no explanation of what 'snapshot data omitted' means for the response.

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?

It is short and front-loads the tool's purpose, but '(snapshot data omitted)' duplicates the title verbatim and consumes space without adding information. Efficient in length, weak in content.

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?

With 0% parameter coverage, no output schema, and many report-related siblings, the description leaves an agent unable to decide between reports_list, reports_get, and publicReports_get or to use the filters 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% for both parameters. The description never mentions 'limit' or 'clientId', so an agent gets no meaning for what clientId filters or what the limit default is; the schema alone leaves both 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?

The verb+resource pair 'List reports' is clear, and the GET endpoint confirms it is a read/list operation. However, '(snapshot data omitted)' is cryptic and unexplained, and nothing distinguishes this from siblings like reports_get, reports_listDeliveries, or reportSchedules_list.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as reports_get for a single report. An agent must infer usage entirely from the name.

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