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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds genuinely useful context the annotations cannot convey: expectedSpecVersion exists to prevent stale writes, revealing optimistic-concurrency semantics. It still omits what happens on a version mismatch (error? retry?) and whether the supplied bubble config replaces or merges with existing bubbles.

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 sentences, no filler, with the core action front-loaded and the concurrency constraint second. Nothing could be cut without losing signal.

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 nested-object mutation tool with no output schema and 0% top-level schema coverage, so the description carries real burden. It leaves unstated whether the config replaces existing bubbles, what the response contains, and what an agent should do when the spec version is rejected.

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 only partly does: it explains expectedSpecVersion's purpose but says nothing about projectId. The nested 'input' object is well annotated in the schema itself (layerId, bubble, linkFilter, artifactsLayer), so the description is not the only source for those.

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 ('Configure bubble interactions for a project map'), so an agent knows it mutates bubble configuration. It does not distinguish itself from adjacent configuration siblings such as project_configure_popup or project_configure_legend, which also 'configure' map presentation.

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 statement of when to use this tool versus project_configure_popup or project_update_layer_style, and no prerequisites or exclusions are given. The only usage-adjacent sentence is about expectedSpecVersion, which is a parameter requirement rather than routing guidance.

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