get_r_report_queries_compliance_internal_checks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the HTTP method and parameter placement but says nothing about pagination behavior, required authentication, failure modes, or what the records represent. It is not contradictory, but it is thin.

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 and contains no obvious fluff, with parameter guidance near the front. However, the phrasing 'Retrieve records Calls `GET /...`' reads like two fragments concatenated, and the rest is generic REST boilerplate rather than carefully tailored content.

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 GET endpoint with no annotations and a generic schema, the agent still lacks the concrete path parameters, query filter names, pagination parameters, and even a basic explanation of what compliance_internal_checks returns. The output schema may cover return shape, but invocation prerequisites are underspecified, especially given the enormous sibling tool list.

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?

The schema offers only generic object containers with 0% description coverage, so any semantic help is valuable. The description does assign roles: path_params holds route IDs, query holds filters/pagination, and headers holds required headers. However, it does not specify the actual route ID parameters, accepted query filter keys, pagination fields, or mention the body parameter.

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 action 'Retrieve records' and explicitly maps the tool to `GET /r/report_queries/compliance_internal_checks`, so the verb, resource, and HTTP method are clear. It does not explain what compliance internal checks are or how this tool differs from sibling compliance report queries, so it stops short of 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?

The description only explains where to place path_params, query, and headers; it does not say when to use this tool versus any of the many sibling report-query tools, nor does it mention exclusions or alternatives. This is mechanical guidance, not usage context.

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