gmb_v4_accounts_locations_media_patch

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

Adds the key detail that updates use an update mask, indicating a partial update. This complements the annotations (readOnlyHint=false, idempotentHint=true) without contradiction, giving useful context beyond the structured data.

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?

A single, front-loaded sentence with the HTTP method, endpoint, and core action. No superfluous words, fitting the conciseness ideal.

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?

While annotations cover safety and idempotency, the description is minimal for a mutation tool: it does not mention what fields can be updated, permissions required, or the format/semantics of the update mask. Given no output schema, this leaves some operational 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 only 33%, and the description provides no details about the 'name' or 'body' parameters beyond referencing MediaItem. It does clarify 'updateMask' usage via 'using an update mask', partially compensating for the low schema coverage.

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?

Clearly states a specific verb+resource: 'Updates media item metadata'. The endpoint pattern and operation distinguish it from the many sibling media tools (create, delete, get, list). No ambiguity about what this tool does.

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 does not explicitly state when to use this versus alternatives, nor does it provide exclusions or alternate tool suggestions. The intended use is implied by the wording but not explicitly guided.

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