Save autosave draft (자동저장 초안)

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

Goes beyond the annotations by disclosing the overwrite semantics of the single autosave slot and the editor's restore prompt, which explains why idempotentHint=false matters in practice. It does not cover auth requirements or how the draft interacts with the draft owner's session, keeping it just short of a 5.

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?

Three short sentences, front-loaded with the core action and non-creation guarantee, then the restore behavior, then the alternative. Every sentence carries distinct information with zero repetition.

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?

With annotations covering the safety profile, an output schema handling return values, and full schema coverage for parameters, the description only needs the semantics an agent could not infer: the single-slot overwrite, the non-creation guarantee, and the restore flow. All are present.

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 100%, so all seven parameters (title, content, blog_url, tags, category, attachments, content_format) are already documented in the schema. The description adds no parameter-level detail beyond the visibility reference for the alternative tool, which is the expected baseline when the schema does the work.

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 and resource: 'Write a draft into the editor's single autosave slot', followed immediately by the negative scope 'No post is created.' This cleanly separates it from siblings like tistory_publish_post without requiring the schemas to be opened.

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?

Explicitly names the alternative and the condition that selects it: 'For several reviewable drafts, publish with visibility=\'private\' instead.' The agent knows both when to call this tool and when to route elsewhere.

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