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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation and non-idempotency profile is covered. The description adds genuine value with the optimistic-concurrency note that expectedSpecVersion prevents stale writes, but it never says what happens on a version mismatch or what the tool does to existing popup config.

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, front-loaded with the operation and followed immediately by the one behavioral constraint that matters. Nothing is wasted or redundant.

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 deeply nested mutation with no output schema and 0% top-level schema coverage, the description is thin: it omits how input.title is used, that a null popup disables popups, and any error/response behavior. Nested field descriptions in the schema fill some gaps, keeping this at a minimum-viable level rather than inadequate.

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?

Measured top-level schema description coverage is 0%, so the description carries the burden. It explains expectedSpecVersion's purpose (stale-write protection) and indirectly maps to input.popup.properties, but projectId and the input wrapper (layerId, title) go unexplained. Partial compensation, not full.

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?

States a specific verb+resource: configuring popup presentation and the feature attributes shown in project map popups. It does not, however, distinguish itself from the obvious siblings geobble_studio_set_basic_popup and geobble_project_configure_bubbles, so an agent must guess which popup tool applies.

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?

No when-to-use or when-not-to-use guidance, and no alternatives are named despite multiple overlapping popup/bubble tools in the sibling list. The only prerequisite hint is that expectedSpecVersion is required, which is stated as a rule rather than as a selection condition.

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