get_report_queries_ad_roles

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does imply a read operation ('Retrieve', 'GET') but does not disclose any quirks, authentication requirements beyond 'headers' (which are vague), rate limits, error behaviors, or what constitutes 'filters' or 'pagination'. The mention of the HTTP method is minor and does not sufficiently cover behavior.

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 but awkwardly punctuated: 'Retrieve ad roles Calls `GET /report_queries/ad_roles`.' – the verb 'Calls' is jarring. It is concise but could be better structured for readability. The key information (path, query, headers) is present but could be presented more cleanly.

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 the output schema exists, return format is covered. However, the description does not clarify what 'ad roles' are, what specific filters are available, pagination mechanics (page size, cursor), or any required headers. It is minimal and leaves the agent guessing about essential invocation details, though it does mention the three parameter groups.

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 description provides valuable parameter context beyond the schema: it specifies that 'path_params' carries route IDs, 'query' holds filters and pagination, and 'headers' contains required request headers. Since the schema has 0% coverage (generic object types with no descriptions), this mapping is essential and significantly aids parameter usage.

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 ('Retrieve ad roles') and cites the exact endpoint ('GET /report_queries/ad_roles'). This is a specific verb + resource pair that distinguishes it from numerous sibling report query tools, especially the more specific 'ad_roles_details' and 'ad_roles_member' variants.

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 use this tool versus alternatives, nor any mention of when not to use it. It does not reference any sibling tools or conditions for selection. The description is purely operational, lacking decision-making context.

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