List saved reports

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

With no annotations, the description carries the full burden. It usefully discloses that the return includes a resource name that run_report consumes, but says nothing about pagination behavior, result limits (pageSize max 200), or whether listing requires specific permissions. Adequate for a simple read but not rich.

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?

Three short sentences, zero filler, with the core action and the downstream dependency front-loaded. Every sentence earns its place.

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?

There is no output schema, and the description compensates by stating what is returned (the resource name) and how it is used next. Pagination behavior is left implicit and not spelled out, keeping it just short of complete for a list tool.

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 100%, so pageSize and networkCode are already fully documented in the schema and the baseline is 3. The description adds no syntax or format detail beyond what the schema provides, though it does clarify what the returned resource name is for.

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 ("List saved reports in Ad Manager") and immediately ties the output to a sibling by naming run_report and the resource name it consumes. An agent can separate this from run_report without opening either schema.

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?

"Use this first to find the report to run" gives explicit sequencing relative to run_report, which is the one alternative that matters here. It stops short of naming exclusions or stating what to do when no reports exist, so it is clear context rather than full when/when-not guidance.

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