list_reports

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the basic action and omits critical details like pagination behavior, default limits, authorization requirements, or sorting order. The schema hints at limit and filter, but the description adds no behavioral context beyond the schema itself.

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 a single, front-loaded sentence with no extraneous information. Every word serves the purpose of defining the tool's function, making it highly concise and efficient.

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?

Given the tool has two parameters with schema descriptions and an output schema, the description could be more complete. It lacks context about the scope of listed reports (e.g., user-specific vs. all accessible), ordering, or pagination behavior. However, the presence of an output schema partially compensates for omitting return value details.

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 coverage is 100%, with both 'limit' and 'filter_name' having descriptions in the input schema. The tool description does not add any further meaning about these parameters beyond what the schema already provides. Thus, the baseline score of 3 is appropriate.

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 'List Visual Analytics reports.' clearly states the action (list) and the resource (Visual Analytics reports). It distinguishes from siblings like 'get_report' (single report retrieval) and 'get_report_image' (image retrieval), making the tool's purpose 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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_report' or 'get_report_image'. There is no mention of use cases, prerequisites, or when not to use this tool, leaving the agent without decision support.

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