Reports_getReports

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions filter-based retrieval and deployment location, but omits whether this is read-only, pagination behavior, permissions required, or what 'report details' actually include. There is no contradiction, but disclosure is minimal.

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 short and mostly front-loaded, but the opening 'Catalog entry.' is filler that does not earn its place. The useful information is delivered in two sentences, which is acceptable but not exemplary.

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?

Critical context is missing: no filter keys, no output shape, no indication of whether a list or a single report is returned, and no relationship to sibling report tools. Given no output schema and no annotations, the description is insufficient for reliable invocation.

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?

The schema declares zero properties but allows additionalProperties true, so the agent has no structured parameter definitions. The description says 'filters that you specify' without enumerating or typing them, leaving the agent to guess valid filter names. Since there are no formal parameters, the description needed to compensate but only gestures at the concept of filters.

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 states that the tool returns report details for reports matching user-specified filters, identifying a list/search behavior with a specific verb and resource. The plural 'reports' and 'filters' imply bulk retrieval, but it does not explicitly differentiate from sibling Reports_getReport.

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 about when to use this tool instead of Reports_getReport, Reports_getReportDocument, or Reports_createReport. The only contextual note is about execution environment, which does not help an agent choose between similar report operations.

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