List query reports

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing the safe read-only nature. The description adds useful behavioral detail by enumerating the standard response fields and indicating it returns all query reports (no filtering). It does not disclose potential edge cases like pagination, but given the simple scope, this is acceptable.

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?

Two sentences with no redundancy. The first sentence states exactly what the tool returns; the second provides a practical usage pointer. Every word 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?

With no output schema, the description compensates by listing the exact fields returned. It also mentions the next step (using the ID with reports_query_report_data), making the tool's role in the workflow clear. The one optional boolean parameter is covered in the schema, so no additional details are needed.

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 single parameter 'raw' is fully described in the schema (100% coverage), so the description does not need to repeat it. The description adds context about the standard curated output, but the raw parameter semantics are already covered by the schema, yielding the baseline score.

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 clearly states the tool retrieves all query reports defined in Endpoint Central, listing the specific fields returned (report ID, label, owner, etc.). It also distinguishes itself from the sibling reports_query_report_data by explaining that the report ID is used with that tool to fetch rows, making the 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 explicitly guides the user to use this tool to list query reports and then use the retrieved ID with reports_query_report_data to fetch rows. This provides a clear when-to-use and points to the alternative tool, even though it does not enumerate all other report-related siblings.

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