get_post

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

Discloses return fields (author, date, board, thread number, subject, content, media) and special num format for ghost posts. No annotations provided, so description carries full burden; it is adequate for a read retrieval 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 sentences: first states purpose, second enumerates return fields. No redundant information, front-loaded with key info.

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?

Describes return format adequately given no output schema. Could mention error handling (e.g., post not found) but overall sufficient for a simple retrieval 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 coverage is 100%, but description adds value by explaining board is shortname and num can include _ suffix for ghost posts. Provides context beyond schema descriptions.

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?

Clearly states the tool retrieves a single post from a 4chan archive by board and post number. Distinguishes from siblings like get_thread (whole thread) and search_archive (search).

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?

Explains use of board (shortname) and num (with ghost post suffix) parameters, implying when to use this tool. Does not explicitly state when not to use or contrast with siblings, but sibling names provide enough context.

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