Get a post (글 조회)

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

Beyond the readOnly/idempotent annotations, it discloses that the body is skin-rendered HTML rather than original markdown and that private posts require the saved session. The warning not to echo content_html back for edits is important behavioral guidance that annotations cannot provide.

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?

Four short sentences, front-loaded with the core return behavior and followed by essential caveats. Every sentence carries useful information with no repetition.

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?

An output schema exists, so return values need not be explained, but the description still covers the important shape of the body and the private-session condition. For a two-parameter read tool, it supplies enough context to call 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%, so blog_url and post_id are already fully documented in the schema. The description adds no parameter-specific syntax or constraints beyond the schema baseline.

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 states a specific verb and resource: return one post's metadata and body HTML, with the admin-list and post-page sources. It distinguishes private-post retrieval via the saved session and points to tistory_update_post for editing, so an agent can separate it from write siblings.

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?

It gives clear context for private posts and an explicit when-not: to edit, write the new body yourself and send it with tistory_update_post rather than echoing content_html back. It does not name tistory_list_posts or tistory_fetch_public_posts as retrieval alternatives, so routing is helpful but not fully exhaustive.

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