gmb_info_locations_attributes_getgoogleupdated

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, providing the safety profile. The description adds valuable context about the data source (Google or user-generated content) and the potential difference from the merchant's version, which goes beyond the annotations without contradicting them.

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 concise, consisting of two short sentences that include the HTTP method and endpoint example for clarity. Every sentence adds meaningful information without redundancy or fluff.

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, the description explains the return value (attributes as live on Google). It conveys the key distinction from the merchant's version, which is crucial for correct use. While it doesn't discuss response structure or pagination, these are not essential for a simple read-only tool.

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?

The schema descriptions cover 100% of parameters, including name, fields, and standard query parameters. The description does not add any parameter-specific semantics, so the baseline of 3 is appropriate; it does not compensate or add beyond the schema.

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 clearly states the tool retrieves live consumer-facing attributes for a location, with the specific verb 'Retrieves' and resource 'attributes for a location'. It distinguishes itself from the merchant's version (e.g., getattributes) by noting the consumer-facing view may differ from the merchant's version.

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 description provides clear context that this tool is for the live Google Maps/Search view, implying when it should be used. However, it does not explicitly name alternative tools or state when not to use it, lacking an explicit exclusion or alternative reference.

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