set_geocoding_context

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no scope (workbook- vs. session-level), no persistence semantics, no statement of whether existing geocoded fields are affected, and no permission requirements. It only conveys that this is a setter influencing generated map coordinates.

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?

It is a single front-loaded sentence with no redundant phrasing or filler. However, the brevity edges toward under-specification rather than genuine economy, so it does not reach a 5.

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?

Although an output schema exists and need not be re-explained, a mutation-style setter with no annotations, 0% parameter coverage, and two undocumented parameters is missing essentials: what the context governs, its scope, and how to format inputs. The description is too thin for the tool's actual 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 0% for both parameters, and the description never mentions them at all. An agent gets no guidance on expected format for country (ISO code vs. name) or state, nor on the interaction between the required country and optional state, so the description fails to compensate for the coverage gap.

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 states a verb and a resource ("Set geographic lookup context"), so the basic action is identifiable, but "geographic lookup context" is abstract and "generated map coordinates" is vague about what is actually affected. It offers no differentiation from the related sibling set_field_geographic_role, which an agent could easily confuse with this tool.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or when-not-to-use. The only hint is the trailing phrase "for generated map coordinates," which implies a context but is too weak to route an agent between this and set_field_geographic_role.

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