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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is known; the description still adds real value by stating 'Changes nothing on Google' (this is a local mapping, not a Google-side mutation) and 'Free on every plan' (no credit cost). It does not say what happens to a previously linked location when a new one is set, which is the main behavioral question left open.

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?

Three short sentences, front-loaded with the primary action, each carrying distinct information (action, unlink variant, no Google-side effect, cost). No filler or restatement of the title.

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 small mutation tool with annotations and no output schema, the description covers the source of the id, the unlink case, side-effect scope, and pricing. The only meaningful gap is the replace-vs-unlink-previous behavior when the site already has a location connected.

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 coverage is 67% and connection_id itself carries no schema description, so the description usefully supplies its provenance and its null semantics. However, it says nothing about site_id or the optional user_goal parameter, leaving the description to add meaning for only one of the three inputs.

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?

Uses a specific verb ('Set') with a precise resource ('which connected Google location this site manages') and explicitly distinguishes the two modes (link by id vs. null to unlink). It is clearly differentiable from nearby siblings like list_google_locations, prepare_google_listing, and connect_data_source.

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?

Tells the agent where to obtain the value ('connection_id from list_google_locations') and documents the alternate unlink path via null, which is exactly the branching an agent needs. There is no explicit statement about when not to use it (e.g. when no Google account is connected), but the context is otherwise clear.

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