gbp_performance_report

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states only that a report is 'generated' — it does not clarify that this is a read-only analytics operation, what metrics the report contains, how far back data extends, or whether generation is immediate or time-consuming. The vague word 'comprehensive' adds no concrete behavioral detail.

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 efficient sentence with no wasted words, which is structurally sound. However, the qualifier 'comprehensive' is filler that provides no real information, and the brevity comes at the cost of missing usage and behavioral context.

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 no output schema and no annotations, the description is the only source of context, yet it does not explain what the report covers, how it relates to gbp_get_insights, or how the locationName parameter should be formatted. For a two-parameter tool with a nested object, this one-liner leaves critical gaps an agent would need to resolve before calling it.

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 only 50%, and the description adds zero parameter information. The schema documents date formats but not the expected resource-name pattern for locationName (e.g., accounts/{id}/locations/{id}) or any date-range constraints, and the description fails to compensate for these gaps.

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 uses a specific verb ('Generates') with a clear resource ('performance report for a GBP location'), which is immediately understandable. However, it does not differentiate from the sibling tool gbp_get_insights, which likely also returns performance-related data for a GBP location, so an agent could plausibly pick the wrong one.

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 offered on when to choose this tool over gbp_get_insights or the other GBP siblings. The description implies a reporting use case but gives no exclusions, prerequisites, or alternative routing, leaving the agent to infer the selection criteria.

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