context.snapshot

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

The description says 'Store the current user context in Blender', which describes a state-changing write operation, while the annotations declare readOnlyHint=true. This is a direct contradiction comparable to the create_record example. The description does not add useful behavioral context beyond the annotations and instead misleads about the side effects.

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?

The description is a single concise sentence that front-loads the core action and result. There is no wasted wording, and the syntactic structure is clean.

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 tool with one optional parameter and output schema, the description still leaves important context unexplained: the role of viewport_id, when to snapshot versus get/restore, and the lifecycle or scope of the returned token. The annotation contradiction also makes the description incomplete and unreliable as a guide.

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?

The description does not mention the viewport_id parameter at all, and schema description coverage is 0%. The schema only provides the title 'Viewport Id' and a null default, which gives no real semantic meaning about what viewport_id selects or how it affects the snapshot.

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 clearly states the action ('Store'), the target ('current user context in Blender'), and the result ('return a session-local token'). It is easy to distinguish from siblings like context.get and context.restore because it frames the tool as creating a snapshot for later use.

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 guidance is given about when to use this tool instead of context.get or context.restore. The description implies a snapshot/restore workflow but does not explicitly state when to snapshot versus when to retrieve or restore context, leaving the selection decision to the agent.

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