Load a saved session

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals what the tool returns (card lines in TCG Live format, named decklists), which is important for an agent to understand the output. It doesn't mention error behavior or side effects, but for a read-only load operation, the format disclosure is significant.

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 two concise sentences, front-loaded with the core purpose and followed by a useful output-format note. Every sentence earns its place with no redundant information.

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?

Given the tool is simple (one parameter, no output schema), the description is complete enough. It explains what the tool does and what the output looks like. Minor gaps like handling of non-existent sessions are not critical for this level of completeness.

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 schema covers the 'name' parameter at 100% with 'Session name as shown by session_list'. The description adds further meaning by tying the parameter to the session_list tool, telling the agent where to obtain valid values. This goes beyond the schema's basic description.

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 states a specific verb and resource: 'Load a saved session by name', distinguishing it from siblings like session_save and session_list. It also specifies the output format (card lines in TCG Live format, decks as decklists), making the purpose fully explicit.

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?

The description provides clear context by mentioning that the output is meant to be pasted into collection_add/check_deck/resolve tools, indicating when this tool is useful. It doesn't explicitly exclude alternatives, but the integration hint gives strong usage guidance.

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