velog_publish_post

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that posts are private and that confirm=true is a write gate, which is real value, but it omits what publishing actually does (irreversibility, whether a URL/slug is returned or reused), auth requirements, and rate limits.

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 tight, front-loaded sentences with no filler. Brevity is a virtue here, though it shades into under-specification for a five-parameter mutation tool.

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 mutation tool with no annotations, no output schema, and zero schema descriptions on five parameters, the definition is too thin. It should at minimum explain urlSlug behavior, what preview returns, and what distinguishes this from the sibling draft tool.

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 five parameters, and the description only explains one of them (confirm). title, body, tags and especially urlSlug (unique? auto-generated? collision behavior?) get no semantic help from either the schema or the 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?

Specific verb pair (preview/publish) plus resource (a private Velog post), so the agent knows this is the posting tool rather than a formatting or listing one. It does not explicitly contrast itself with the sibling velog_create_draft, leaving the publish-vs-draft distinction to inference from the name.

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?

'Writing requires confirm=true' implies a preview-first flow and tells the agent one gating condition. It never states when to call this instead of velog_create_draft, nor whether confirm=true can be set on the first call or whether a preview must precede it.

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