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 fully covered and 'read-only' in the description is largely redundant. The description adds the inclusive date-range semantics, but says nothing about rate limits, per-location scoping when a project has multiple locations, or behavior for unavailable metrics.

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 first sentence is well front-loaded and dense, but the second sentence repeats all eleven enum values verbatim from the input schema, adding length without new information. Roughly half the description is schema duplication.

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 4-required-parameter read tool with 100% schema coverage and no output schema, the description covers inputs adequately but omits anything about the return shape (per-day metric rows, units, zero-fill behavior), date-range limits, or how the 'linked location' is resolved. Adequate but with clear gaps.

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 all four parameters are already documented in the schema, including the enum of valid metric values. The description's enumeration of the 11 metrics duplicates the schema enum rather than adding meaning; the 'inclusive' framing for startDate/endDate also already appears in the schema. Baseline 3 is appropriate.

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 names a specific verb (read), a specific resource (Business Profile Performance API metrics), and the exact scope (the project's linked location over an inclusive date range). It is clearly distinguishable from siblings like get_gbp_profile, get_gbp_reviews, and get_gbp_optimization 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?

Usage is implied by the purpose statement — call this to pull daily GBP performance metrics — but there is no explicit when-to-use guidance, no mention of alternatives such as get_gbp_profile for profile data, and no stated prerequisite that a GBP connection must exist. The reference to 'the project's linked location' hints at a prerequisite but never says so.

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