ad_manager_li_get_ad_analytics

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the safety profile. However, the description adds no behavioral context beyond 'Get ad analytics'—it does not mention any default behavior (like locationId defaulting to GHL_LOCATION_ID), return format, pagination, or other side-effects. Given the low bar because annotations already cover safety, the description still fails to add meaningful behavioral transparency.

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 extremely short ('Get ad analytics') but this is under-specification rather than effective conciseness. It does not front-load any important detail; it merely restates the tool name. The single sentence does not earn its place because it adds no value over the name itself.

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 7 parameters, no output schema, and a large set of sibling analytics tools, this description is wholly inadequate. It does not explain what analytics are returned, how to interpret the response, or how this tool differs from ad_manager_li_get_campaign_group_reporting, ad_manager_li_get_reporting_list, and similar. An agent cannot correctly select or invoke this tool 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?

Schema coverage is 100%—all seven parameters have descriptions, including date formats, enums for pivot and groupBy, and defaults for locationId. The description itself adds nothing beyond the schema. Since schema coverage is high, the baseline of 3 applies, and no extra credit is warranted because the description does not enhance parameter understanding.

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 states a verb ('Get') and a resource ('ad analytics') but is extremely generic. It does not specify what kind of analytics, which ad platform, or how it differs from siblings like ad_manager_li_get_campaign_group_reporting or ad_manager_li_get_reporting_list. It essentially restates the tool name with minimal added detail, making it difficult for an agent to distinguish among the many analytics-related tools.

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?

No guidance is provided about when to use this tool versus any of the numerous sibling reporting/analytics tools. There is no mention of conditions, alternatives, or exclusions. An agent has no help deciding between this and ad_manager_lt_get_campaign_group_reporting, ad_manager_google_get_reporting, etc.

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