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

Annotations already declare non-read-only, non-idempotent, non-destructive. The description adds genuinely new context: the save path mutates project-level default state and expectedSpecVersion acts as an optimistic-concurrency guard against stale writes. It lacks detail on what a version mismatch returns, but that is a real addition beyond structured fields.

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, and the primary capability is front-loaded before the concurrency caveat. Every clause carries information the caller needs.

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 with no output schema and two distinct modes, the definition covers the conceptual core but omits failure behavior on a stale expectedSpecVersion, what happens to an existing default view on save, and any permission requirements. Adequate but with clear 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%, though nested fields (action, title, timing) are self-documenting. The description usefully explains the one opaque parameter, expectedSpecVersion, but says nothing about projectId or the shape of the input/camera union.

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 concrete verb+resource ('navigate the live project camera', 'persist a default view') and captures both operating modes, which is more than the title alone. It stops short of distinguishing itself from near neighbors such as geobble_project_configure_camera or geobble_map_view, so the agent must infer the boundary.

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?

It implies two usage modes (live navigation vs. persisted default) but never states when to choose one over the other, nor when to reach for the sibling camera/map-view tools. The navigate-vs-save semantics are only spelled out in the schema's action enum, not in the description.

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