Sessionplan

The two tools are a clean encode/decode pair: create_session_link writes a snapshot from a full session object, decode_session_link reads a URL/hash/code back into a session. Their descriptions explicitly state the handoff pattern (decode, modify, then create) so there is no realistic misselection.

Both names follow the same verb_noun pattern with a shared noun (create_session_link, decode_session_link), and the verbs precisely describe the actions. No style mixing or ambiguity.

Two tools is thin in absolute terms, but the domain is deliberately narrow (immutable snapshot links) and each tool covers one half of a complete round trip. Nothing here is redundant or filler, though a third operation would feel less minimal.

The create/read lifecycle is fully covered, and the immutability rule is documented rather than left as a dead end. Minor gaps exist around managing or listing previously created snapshots, but the core workflow has no dead ends.