get_r_report_queries_compliance_check_company_count

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about return shape, pagination defaults, required auth, or whether the endpoint aggregates across companies or just counts. The phrase 'Retrieve records' is generic and gives no behavioral detail beyond what the endpoint path already implies.

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, but its brevity is under-specification, not conciseness. The single sentence mostly restates the endpoint URL and parameter-container mapping, wasting space on generic REST mechanics while omitting tool-specific meaning.

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 an output schema exists but the input schema is a set of untyped catch-all objects, the description was the only place to document meaningful parameters and behavior, and it failed to do so. An agent has no way to know what filters, pagination keys, or route IDs are valid. This is inadequate for a working REST call.

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 generic 'additionalProperties: true' containers, so the schema provides no semantics either. The description merely repeats that route IDs go in path_params, filters and pagination in query, and headers in headers. It does not identify specific query parameter names, expected value formats, or what a valid path_params entry looks like.

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 starts with 'Retrieve records' and then immediately dumps the raw endpoint path without explaining what the resource actually is. The tool name suggests a compliance check company count, but the description doesn't state what a company count is, what filters are meaningful, or how this differs from the many sibling report query tools. It's a generic fetch statement rather than a clear, resource-specific explanation.

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 gives no guidance on when to choose this tool over siblings like get_r_report_queries_compliance_check_asset_count or get_r_report_queries_compliance_count. It only instructs where to place parameters. No exclusions, prerequisites, or alternative routing are provided.

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