get_r_report_queries_asset_compliance_details

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

There are no annotations, so the description must carry the behavioral disclosure burden. It does disclose the HTTP method (GET) and that records are retrieved, but it does not mention authentication requirements, pagination behavior, or any other side effects or constraints beyond '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 description is short and front-loaded with the action and endpoint. The second sentence provides useful parameter-placement guidance without unnecessary fluff, though the phrasing 'Retrieve records Calls GET' is slightly awkward.

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?

Even though an output schema exists, the description is not sufficient to invoke the tool correctly. It fails to specify which route IDs are valid, what filters and pagination parameters are accepted, and what headers may be required, leaving the agent to guess from an arbitrary-object schema.

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%, so the description must compensate. It does add meaning by mapping path_params to route IDs, query to filters/pagination, and headers to request headers, but it never identifies specific parameter names, accepted filter keys, or pagination conventions.

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 the verb 'Retrieve' and names the exact endpoint '/r/report_queries/asset_compliance_details', so an agent knows this is a read operation for that specific resource. It does not, however, explain what 'asset compliance details' actually represent or how this differs from sibling compliance-related report queries.

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 implies the tool is used when retrieving asset compliance detail records, and it gives practical guidance on where to place route IDs, filters, pagination, and headers. It provides no explicit when-to-use versus alternatives, and there are many sibling report-query tools that could overlap.

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