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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds one genuinely behavioral detail beyond them: expectedSpecVersion exists to prevent stale writes, i.e. optimistic concurrency. However it does not say what happens on a version mismatch, whether the update is a partial merge, or what permissions are needed, so the addition is modest.

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?

Two short sentences, zero filler, with the core action front-loaded and the concurrency caveat second. Slightly undersized for a tool with a deep nested settings object, but nothing in it is wasted.

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 mutation tool over a complex nested settings object with no output schema, the description covers the action and the version guard but omits conflict/error behavior, merge semantics, and any permission requirements. Combined with annotations that carry the safety profile and a schema that documents the settings keys, it is adequate but leaves real 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?

Top-level schema description coverage is 0%, so the description must compensate, and it does explain the purpose of one of the three required params (expectedSpecVersion). projectId and the nested input envelope get no help from the description, though the nested settings object is well documented in the schema itself. Partial compensation earns the baseline.

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 names a specific verb and resource ("Update Studio-owned map settings") and adds a scope qualifier, "Studio-owned", that implicitly separates it from the sibling geobble_project_update_settings. It also notes the contour-lines coverage, which tells the agent what kind of settings are involved. It stops short of naming the sibling explicitly, so it is clear but not fully self-differentiating.

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 "Studio-owned" qualifier gives implied routing guidance against geobble_project_update_settings, but there is no explicit when-to-use/when-not statement or prerequisite list. The agent must infer that this tool applies only to Studio-owned maps rather than being told.

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