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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb '조회' and tool name 'get_post' imply a read-only operation, and '전체 내용' indicates the response scope. But it does not mention authentication needs, post visibility rules, or potential side effects. The gap is moderate for a simple read 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 one short declarative sentence that front-loads the action and resource. There is no redundancy, filler, or repetition of schema details.

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 one-parameter read operation with no output schema, the description is nearly complete: it identifies the lookup key and states that the full content is returned. It lacks explicit response structure and error semantics, but those are not essential for basic invocation.

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?

The single required parameter 'id' is already fully documented in the input schema with type, format, pattern, and a Korean description, giving 100% schema description coverage. The description adds no additional semantic meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: '게시글 ID로 전체 내용을 조회합니다' (retrieve full content by post ID). It clearly scopes the operation to a single post identified by ID, which distinguishes it from search-oriented siblings like search_posts or get_feed.

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 usage context is implied: use this tool when you already have a post UUID and need the full post content. However, it does not explicitly state when not to use it or point to alternatives such as search_posts, get_feed, or get_user_profile.

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