velog_create_draft

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

No annotations are provided, so the description carries the full burden. It usefully discloses that created content is a private draft (not published) and that a confirm gate guards the write, which is meaningful behavioral context. It omits auth requirements, what preview returns, and behavior on slug conflicts, so disclosure remains incomplete for a mutating tool.

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 short, front-loaded sentences with zero filler. The purpose leads and the gating constraint follows immediately.

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 5-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It doesn't clarify urlSlug/tags semantics, preview return shape, or failure modes, so an agent cannot call it with full confidence.

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 0% across 5 parameters. The description explains only 'confirm' (must be true for writing); title and body are self-evident, but tags and especially urlSlug receive no semantic explanation anywhere, leaving notable gaps.

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 ('create a private Velog draft') and disambiguates draft from published content via 'private'. It does not explicitly name velog_publish_post as the publish alternative, but the draft/private framing implicitly differentiates it from the publish sibling.

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 sentence 'Writing requires confirm=true' gives a concrete gating condition for when actual creation occurs, and 'Preview or create' implies confirm=false yields a preview. However, it never states when to use this vs. velog_publish_post or how preview output differs, leaving usage coverage partial.

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