벨로그 글 수정

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

The description explains the critical behavioral nuance that body must be sent in full even for partial edits, which is beyond the annotations (readOnlyHint=false, openWorldHint=true). This adds significant transparency for a mutation 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?

The description is two sentences, front-loaded with purpose, and every word earns its place. No redundant or missing information.

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 the 9 parameters, write operation, and presence of an output schema, the description covers all necessary behavioral aspects: required field, partial update semantics, and the body caveat. It is complete for an agent to use correctly.

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% with detailed descriptions for each parameter. The description summarizes the partial update pattern but does not add new per-parameter details. The warning about body being full is already implicit in the schema 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?

The description clearly states the tool updates an existing post, specifies the required parameter (post_id), and explains partial update behavior. This distinguishes it from sibling tools like velog_publish_post (create) and velog_delete_post (delete).

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 tells the agent that only passed fields change and body must be sent in full. It implicitly guides when to use this tool (when an existing post ID is available), but could explicitly mention alternatives like velog_publish_post for new posts.

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