get_r_report_queries_ports_assets_details

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read operation and 'filters and pagination in query' hints at list-style behavior, but there is no disclosure of return semantics, required authentication, rate limits, or any side effects. This is comparable to the update_drive calibration case, which scored 2 under the same zero-annotation burden.

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 short and the parameter-routing sentence is efficient. However, the first sentence has a grammatical concatenation glitch ('Retrieve records Calls GET ...') that reads awkwardly and reduces clarity. The content is appropriately sized but the structure/flow is slightly defective.

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?

An output schema exists, so return-value documentation is not the description's burden, and the parameter routing is covered. What's missing is the conceptual identity of the resource: nothing explains what ports/assets details this query surfaces or why it exists among roughly a hundred similar report-query siblings, so an agent cannot confidently select it based on the description alone.

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 0% and the schema parameters are empty generic objects, so the description must compensate. It does add real value by mapping each parameter to its role: route IDs in path_params, filters and pagination in query, and request headers in headers. But it stops short of naming specific filters, acceptable header keys, or required vs optional fields, leaving the agent to guess.

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 verb and resource: 'Retrieve records' via the explicit endpoint `GET /r/report_queries/ports_assets_details`. This is unambiguous about the mechanical operation. However, it does not differentiate this tool from the dozens of similarly-named get_r_report_queries_* siblings (e.g., get_r_report_queries_ports_view, get_r_report_queries_asset_ports_view), nor explain what 'ports_assets_details' conceptually returns.

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?

No when-to-use vs alternatives guidance is provided. The second sentence gives parameter placement instructions, but nothing tells an agent why it should choose this report query over the many other report_queries tools, or when it should not.

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