get_r_report_queries_lightweight_assets

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

With no annotations provided, the description carries the full burden of disclosing behavior. It indicates a read-only GET operation via 'Retrieve' and 'Calls GET', but it does not mention authentication requirements, pagination behavior, response shape, or any constraints on filters. The description is too thin to be behaviorally transparent.

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 two sentences with no filler. The core action and endpoint are front-loaded, and the parameter placement guidance is expressed compactly.

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 generic schema and complete absence of annotations, the description is not complete enough for an agent to confidently invoke the tool. It omits what 'lightweight_assets' means, what actual query filters are supported, whether path_params are even relevant for this endpoint, and how this differs from similar report-query endpoints. The presence of an output schema covers return values, but too much request-side context is missing.

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 has 0% description coverage and generic open-object parameters, so the description must compensate. It does provide some meaning by mapping path_params to route IDs, query to filters and pagination, and headers to required request headers. However, it does not specify actual path parameter names, available filter keys, pagination parameters, or the role of the body parameter, so compensation is only partial.

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 a clear action ('Retrieve records') and names the exact endpoint (`GET /r/report_queries/lightweight_assets`), which makes the resource and operation identifiable. It does not, however, explain what distinguishes 'lightweight_assets' from the many sibling report-query tools, so it is clear but not fully differentiating.

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_r_report_queries_assets or get_r_report_queries_asset_stats. It only explains how to structure the request envelope, not under what conditions this endpoint is the right choice.

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