hwp_session_state

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

Without annotations, the description carries full burden. It discloses the file path (~/.hwp_studio_state/{session_id}.json), persisted fields, and modes. However, it lacks details on overwrite behavior, cancellation effects, or error handling.

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 concise, front-loading the purpose and adding details in a single paragraph. It could benefit from bullet points for modes, but overall it's efficient and informative.

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 no output schema and no annotations, the description covers storage location, persisted fields, and all modes. It lacks error handling or size limits but is adequate for a state management tool with 3 parameters.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the mode enum (save/load/list/delete/cancel) and auto-generation of session_id. It clarifies the state object structure beyond schema field names.

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 tool saves/resumes progress of long writing tasks, with a specific verb ('저장/재개') and resource (session state). It distinguishes from sibling tools by focusing on session persistence rather than document editing.

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 indirectly implies usage through mode enumeration (save, load, list, delete, cancel). While it doesn't explicitly state when not to use or name alternatives, the context of long tasks provides clear direction.

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