ad_manager_google_get_reporting

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds zero behavioral context—it does not disclose return format, pagination, date formatting, or any other traits that an agent would need to anticipate the tool's 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 only three words, but this is under-specification rather than concise, effective writing. It lacks any structured information such as a clear scope or usage note, making it unhelpful despite its brevity.

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 six parameters (four required) and no output schema, this description is grossly inadequate. It fails to explain what reporting data is returned, how dates are formatted, what fields like 'cost_micros' represent, or how the groupBy parameter affects results. An agent cannot call this tool correctly based on this description alone.

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 provides 100% description coverage for all six parameters, so the agent has baseline documentation. The description adds no additional meaning or clarification beyond what is already in the schema, so it earns the baseline 3 for high coverage.

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 'Get reporting data' is a generic phrase that merely restates the tool name without specifying the resource (Google Ads reporting) or its scope. It does not distinguish this from sibling reporting tools like ad_manager_google_get_reporting_list or ad_manager_google_get_campaign_reporting, leaving the agent uncertain about what exactly this tool retrieves.

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 the many alternate reporting tools. The description does not mention any exclusions, prerequisites, or alternatives, so an agent cannot determine the appropriate context for invoking this specific function.

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