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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds real behavioral context the annotations lack: results are per single location, returned with daily granularity, and broken out by channel and device. It stops short of discussing auth scope, rate limits, or date-range limits.

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 resource and scope, with no filler. The metric enumeration is a long comma-separated run that is slightly heavy but it is information-dense and each item earns its place.

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?

With three required params, no output schema, and simple flat inputs, the description compensates well by describing the returned metric set and daily granularity. It covers what an agent needs to call and interpret the tool, though it is silent on limits such as maximum date span.

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%, with date format (YYYY-MM-DD) and the origin of gbp_location_id ('From gbp_list_locations') documented in the schema itself. The description only restates 'one location' and 'date range' without adding format or constraint detail, so the baseline 3 applies.

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?

States a specific resource (Business Profile performance), a precise scope (one location over a date range), and enumerates the returned metrics (impressions by channel/device, calls, clicks, directions, conversations, bookings). This is clearly distinguishable from siblings like gbp_list_locations, gbp_reviews, and gbp_posts without opening any schema.

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?

The closing clause 'Use for client reporting beside Ads and Analytics' gives one usage context and faintly points at sibling reporting tools (ads_report, ga4_report), but never names them or states when this tool should not be used (e.g., multi-location aggregation). Usage is implied rather than specified.

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