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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the mutation profile is covered structurally. The description adds genuinely new behavioral context the annotations lack: the optimistic-concurrency contract ('expectedSpecVersion is required to prevent stale writes'), i.e. that a stale version will be rejected. It still omits what happens to any pre-existing camera config and whether the change can be undone.

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 purpose statement is front-loaded ahead of the versioning constraint. Every sentence earns its place.

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 nested mutation tool with no output schema and 0% schema description coverage, the description is too thin: it neither explains the input payload (camera trigger/delay/center semantics beyond the schema's brief inline notes) nor what the call returns or how a rejected stale version surfaces.

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% and there are three required params (projectId, expectedSpecVersion, input with nested layerId/camera). The description explains the purpose of only expectedSpecVersion; projectId, input, layerId and the camera object semantics are left entirely to the raw schema, so it does not 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?

States a specific verb+resource: 'Configure camera interaction behaviour for a project map.' An agent can distinguish this from sibling configurators like geobble_project_configure_popup or configure_legend on the strength of 'camera interaction behaviour' alone, though it never names those siblings.

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 guidance, no prerequisites, and no routing to or away from the many sibling configure_* tools. The only usage-adjacent note is that expectedSpecVersion is mandatory to avoid stale writes, which is a constraint rather than situational guidance.

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