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

No annotations are provided, so the description carries the full burden, yet it says nothing about read-only behavior, permissions, pagination, or what happens when the optional date range is omitted. '(GraphQL)' hints at the transport but conveys no operational 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?

It is a single fragment with no wasted words, but it is under-specified rather than efficiently concise. There is no front-loaded verb or scope sentence an agent can act on.

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 5-parameter reporting tool with no annotations and no output schema, the description should explain date-range defaults and what metrics are returned. It does neither, so an agent must open the schema and guess at behavior.

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 description coverage is 100%, so campaign_id, adam_id, report_start_time, report_end_time, and notification_message are all documented in the schema. The description adds nothing beyond that, which is the baseline case when the schema does the heavy lifting.

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 the resource ('Ad group metrics') and the scope ('for a campaign'), which is more than a tautology. But it uses no verb ('list'/'retrieve'), and it never distinguishes itself from the very similar sibling list_campaign_reports or from list_ad_groups, leaving the agent to infer the difference.

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 statement of when to use this tool rather than list_campaign_reports, list_ad_groups, or get_campaign. The '(GraphQL)' tag is an implementation note, not usage guidance, so the agent gets no routing help.

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