gmb_info_locations_patch

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

The description only says 'Updates', which is consistent with annotations (readOnlyHint=false), but it adds no extra behavioral context such as the requirement for updateMask, the use of validateOnly for validation-only requests, or the partial-update semantics of PATCH. Annotations already imply a write operation, so the description adds minimal value.

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 and front-loaded with the HTTP method and resource, but it is too sparse for the complexity of the tool. It has no wasted words, yet lacks the detail needed for effective agent decision-making.

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?

This is a complex tool with 8 parameters and nested objects, and no output schema. The description fails to mention critical details like the required updateMask parameter, the validateOnly option, or what the response contains, making it completely inadequate for the tool's complexity.

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%, and the input schema thoroughly documents all parameters including the required updateMask. The description itself adds no information about parameters, so the baseline of 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?

The description clearly states the tool updates a specified location, using a specific verb (PATCH) and resource (location). This distinguishes it from sibling tools like gmb_info_locations_get and gmb_info_locations_delete, making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives, no exclusions, and no mention of preconditions or parameters like updateMask. It merely states the action without context.

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