벨로그 글 발행

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

Annotations already indicate destructiveHint=true, and the description adds key behavioral details: it bypasses drafts, publishes only as private under the current settings (requires VELOG_ALLOW_PUBLIC=1 for public), and can be reverted via unpublish. This goes beyond the annotations and provides useful context for an agent.

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?

Two concise sentences, front-loaded with the main action. The additional notes on privacy and revert are valuable and do not waste words.

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 publish/mutation tool, the description covers the core behavior, the current environment restriction, and the revert path. No output schema exists, so mentioning the revert is helpful. It could have noted what is returned on success, but that is a minor gap given the action context.

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?

Input schema has 6 parameters with only 33% coverage; title and body lack descriptions. The description does not mention any parameters or offer guidance on how to fill them. Tags, url_slug, series_id, and thumbnail have schema descriptions, but required fields are undocumented. The description fails to compensate for the coverage gap.

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?

Description states '새 글을 바로 발행한다' (publishes a new post immediately), using a specific verb and resource. It distinguishes from velog_publish_draft by explicitly saying it does not go through a draft, and from velog_unpublish_post by noting it can be reverted.

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?

Provides clear context for when to use this tool: publishing a new post directly without a draft. It also names velog_unpublish_post as the alternative for reverting. Does not explicitly compare to velog_publish_draft, but the draft distinction implies when each should be used.

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