get_r_report_queries_asset_critical_vulnerabilities

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

With no annotations, the description carries the full transparency burden. It does disclose the HTTP method (GET) and that the call retrieves records, but it does not mention authentication requirements, rate limits, pagination behavior, or any required headers despite vaguely referring to 'required request headers.'

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 definition is short and front-loads the endpoint, which is good. However, the first sentence is grammatically malformed ('Retrieve records Calls `GET...`') and the structure is choppy, mixing a fragment with an instruction.

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?

The output schema covers return values, but the description still omits endpoint-specific parameter details, usage context, and auth/header expectations. Given the large sibling list and 0% schema coverage, an agent cannot confidently construct a correct request beyond calling the URL with empty parameters.

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 0% and all four parameters are opaque generic objects. The description adds only boilerplate placement advice—'filters and pagination in query'—without naming a single valid filter, route ID, or header. It also suggests placing route IDs in path_params even though the endpoint path contains no path parameters, which can mislead.

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 names a concrete action ('Retrieve records') and the exact endpoint, /r/report_queries/asset_critical_vulnerabilities, so the resource is identifiable. It does not explicitly contrast with the many sibling get_r_report_queries_* tools, so it stops short of full differentiation.

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 only instructs where to place parameters ('route IDs in path_params, filters and pagination in query...'). It gives no guidance on when this tool is appropriate, what conditions select it, or which siblings are alternatives. For an agent facing dozens of similar report-query tools, this is insufficient.

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