get_r_report_queries_application_count

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

No annotations are present, so the description carries the full burden. It reveals that this is a read operation via `GET`, but it does not disclose response behavior, pagination defaults, authentication needs, rate limits, or failure modes. It adds almost nothing beyond the basic operation.

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 a single compact sentence that front-loads the action and endpoint, then gives parameter placement guidance. The wording is slightly awkward ('Retrieve records Calls ...'), but nothing is wasted.

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?

For a tool with no annotations, four generic object parameters, and a large sibling family, the description is too thin. It omits concrete path/query/header details and expected output semantics, so an agent would need external knowledge to call it reliably.

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 does add a useful mapping: route IDs go in `path_params`, filters and pagination go in `query`, and required request headers go in `headers`. However, it does not name concrete route IDs, query parameter keys, or header values, so an agent still cannot construct parameters confidently.

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 identifies the resource (`report_queries/application_count`) and a clear verb (`Retrieve`), and gives the HTTP endpoint. It is clear enough on its own, but it does nothing to differentiate among the large family of `get_r_report_queries_*` siblings beyond the resource name.

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?

There is no guidance about when to call this endpoint instead of sibling report-query tools, nor are there exclusions, prerequisites, or alternative recommendations. The only contextual hint is the endpoint/name itself, which the agent must interpret on its own.

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