get_report_queries_ad_group_users

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

With no annotations, the description carries the full burden, but it only states 'Retrieve' and the endpoint. It does not disclose authentication requirements, potential rate limits, response size, or side effects. Since this is a read operation, 'Retrieve' implies idempotence, but the lack of behavioral detail leaves gaps.

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?

Two sentences, front-loaded with the action and endpoint. It wastes little space and conveys the essential calling pattern. The wording 'Calls GET /report_queries/ad_group_users' is a minor redundancy but not harmful.

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 sits among dozens of report query siblings and the description gives no clue about what an 'ad group user' is or which scenario requires this dataset. With an output schema present, it needn't explain return values, but it should at least note the required auth/prerequisites or clarify the data scope.

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 defines the roles of path_params (route IDs), query (filters and pagination), and headers (required request headers). However, it does not detail specific keys or formats, and 'body' is completely ignored, leaving part of the parameter space undefined.

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 clearly states the action and resource: 'Retrieve ad group users' and explicitly names the endpoint. However, it does not differentiate from the many sibling report query tools, such as get_report_queries_ad_groups_view or get_report_queries_get_user_details, so it is not fully distinct.

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?

There is no guidance on when to choose this tool over related tools. It only provides a generic instruction to put route IDs in path_params, filters in query, and headers in headers, which is procedural rather than contextual. No alternatives or condition for use are mentioned.

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