close_post

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the archiving action and the lock nuance ('prevents reopening'), but it does not disclose whether archiving is reversible, what permissions are needed, or how it affects replies or other content.

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 short sentences with zero wasted words. The core action is front-loaded, and the lock parameter explanation is placed second as a useful optional clarification.

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 simple two-parameter tool with no output schema and no annotations, the description is minimally adequate: it states the operation and the key behavioral option. It lacks explicit guidance on when to use, permissions, return value, and undo semantics, but is usable for straightforward 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?

Schema description coverage is 0%, so the description must compensate. It adds meaning for lock by explaining that lock=True prevents reopening, but thread_id is left implicit as 'a forum post.' The parameter names are self-explanatory, but the description does not fully elaborate on either parameter.

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: 'Archive a forum post.' This clearly distinguishes close_post from create_post, reply_post, and read_post, so an agent knows exactly what operation is invoked.

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 implies use when the agent needs to archive a post, but it does not explicitly state when to choose this over alternatives like deletion, nor does it mention any exclusions such as permission requirements or whether it applies only to certain post states.

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