get_r_report_queries_compliance_check_count

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Retrieve records' and the endpoint, implying a read operation but not stating the return format or potential errors. The description does not contradict annotations (none provided), but it fails to provide any behavioral context such as pagination, rate limits, or whether it returns a single count or a list. The gap is severe for a tool with zero annotations.

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 sentence with a clear structural breakdown: it states the endpoint and then distributes parameters across path, query, and headers. It is concise and front-loaded with the key action. However, it lacks useful context, so it is efficient but not information-dense.

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?

The tool has an output schema (unknown content) and complex context with many sibling report query tools. The description does not specify what the count represents, how to interpret the response, or any examples. Given the prevalence of similar compliance-related endpoints, the description is too thin to allow correct selection and invocation, especially without annotations or detailed 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%, and the schema defines only generic container parameters (body, query, headers, path_params) with no specific field names or types. The description adds minimal semantic meaning by saying 'Provide route IDs in path_params, filters and pagination in query, and any required request headers in headers.' This is generic and does not explain what the route IDs are, what filters are available, or what the body might contain. This is insufficient to compensate for the lack of schema details.

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 tool retrieves records via the endpoint `/r/report_queries/compliance_check_count`, which indicates it fetches compliance check count data. However, it does not explicitly define what 'compliance_check_count' means, nor does it differentiate from the many similar report query siblings like `get_r_report_queries_compliance_check_asset_count` or `get_r_report_queries_compliance_check_company_count`. The verb 'Retrieve' and the endpoint are clear, but the resource semantics are vague.

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 minimal guidance: 'Provide route IDs in path_params...' for path parameters, but does not specify when to use this tool versus alternatives like `get_r_report_queries_compliance_check_asset_count` or `get_r_report_queries_compliance_count`. The context signals show no usage conditions, no exclusions, and no mention of alternatives. A determined agent might infer it's for compliance check counts, but without explicit guidance, confusion with similar siblings is likely.

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