get_r_report_queries_total_asset_count

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

There are no annotations, so the description carries the full behavioral burden, but it only says 'Retrieve' and 'GET', implying a read operation. It does not disclose response semantics, authentication requirements, or side effects, leaving behavior largely inferred.

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 compact and front-loads the endpoint, which is efficient for an agent. The grammar is slightly awkward ('Retrieve records Calls ...'), but the length is appropriate and there is no unnecessary filler.

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 annotations and a fully generic schema, the description should provide more invocation context, but it only gives the endpoint and parameter placement. The body parameter is unaddressed, route ID requirements are vague, and no usage context distinguishes it from dozens of sibling report-query tools. The output schema exists, so return-value detail is not required, but the surrounding context is insufficient.

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?

With 0% schema description coverage, the description partially compensates by assigning path_params to route IDs, query to filters/pagination, and headers to required headers. It omits the body parameter entirely and gives no concrete filter names or pagination syntax, so the semantic value is limited.

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 the exact endpoint (`GET /r/report_queries/total_asset_count`) and uses a clear verb ('Retrieve'), so an agent can identify the resource. However, 'records' is vague for a count endpoint, and the description does not explicitly differentiate this from sibling report-query tools beyond the URL.

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 guidance or alternative tools are mentioned; the description only maps parameters to request locations. Without usage context or sibling differentiation, an agent cannot determine when to select this over other report-query tools.

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