gmb_info_locations_get

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds valuable context about data source and freshness ('as last set by the merchant', 'may not reflect updates from Google or user-generated content'), which is beyond the annotations and sets accurate expectations for the response.

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 sentence preceded by the HTTP method, which is somewhat redundant but not padding. The caveat about Google updates is essential and earns its place. There is zero waste and information is front-loaded.

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 simple GET-by-name operation with a rich schema and detailed annotations, the description is adequate. It clearly states what is returned and provides a key limitation. Without an output schema, it could mention the response format, but the low complexity makes the description sufficiently complete.

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 the baseline is 3. The description does not add parameter-specific semantics; it only echoes the 'name' path parameter already described in the schema as 'The name of the location to fetch' and adds no additional meaning for fields, readMask, or other parameters.

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 'Returns the specified location as last set by the merchant', providing a specific verb and resource. It also distinguishes this tool from siblings like getgoogleupdated by emphasizing the merchant-set viewpoint, making its purpose distinct.

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 explicitly says the returned data may not reflect Google or user-generated content, giving a clear when-not-to-use condition. It also implies when to use it: when you need the merchant's last set version. This provides explicit usage guidance even without naming alternatives.

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