get_r_report_queries_compliance_maturity

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

With no annotations provided, the description carries the full behavioral burden. It does convey that this is a read operation via GET, that pagination is supported, and that headers may be required. However, it omits specifics such as required auth headers, rate limits, or any response behavior beyond the output schema.

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 compact and front-loads the endpoint and core action. It earns its length by providing parameter placement instructions. The phrasing 'Retrieve records Calls' is awkward but does not substantially impair readability.

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, a generic opaque schema, and no semantic explanation of the resource, the description is not enough to call the tool with confidence. Missing context includes what compliance maturity records represent, which route IDs apply, which headers are required, and how this report differs from related report-query endpoints.

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 coverage is 0%, so the description must compensate. It adds meaningful role information by mapping route IDs to path_params, filters/pagination to query, and request headers to headers. It does not name specific filter or pagination parameters, and the mention of route IDs is confusing for an endpoint with no visible path placeholders.

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 a specific verb ('Retrieve') and an exact endpoint ('GET /r/report_queries/compliance_maturity'), so an agent can tell it fetches compliance-maturity report records. However, it does not explain what compliance maturity means or differentiate it from the many sibling report-query tools beyond the endpoint 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?

The description gives structural invocation guidance ('Provide route IDs in path_params, filters and pagination in query...') but no guidance on when to choose this tool over alternatives. There is no exclusionary context or mention of sibling tools.

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