get_r_report_queries_compliance_count

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

No annotations are provided, so the description must carry the behavioral burden. It only says 'Retrieve records' and specifies a GET method, implying a read-only operation, but it doesn't disclose any authentication, rate limits, or output characteristics. Given the lack of annotations, this is a significant gap.

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 two sentences and relatively compact, but the phrase 'Retrieve records Calls' is awkwardly worded, suggesting a possible typo. It conveys the essential parameter placement but could be better structured.

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 no annotations and a large sibling set, the description is sparse. It doesn't explain what the compliance count represents, which route IDs are allowed, what filters exist, or what the response contains. While an output schema exists, the description still omits operational details like required auth headers, making it incomplete for a tool in this large API surface.

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%, but the description compensates partially by mapping `path_params` to route IDs, `query` to filters/pagination, and `headers` to required headers. It does not describe specific parameter names, formats, or which filters are available, so the compensation is incomplete.

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 specific endpoint and states it retrieves records, giving a clear resource and read verb. However, it doesn't explain what a 'compliance count' is or differentiate it from many sibling report query tools, so it's not a 5.

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?

It instructs where to provide path parameters, query filters/pagination, and headers, which is useful. But it provides no guidance on when to use this tool versus the many other report query siblings, and no explicit exclusions. Thus the usage context is thin.

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