modify_forum_post

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

No annotations are provided, so the description must carry full behavioral disclosure, but it does not mention permissions, side effects, reversibility, or the audit-log reason parameter. It identifies the operation as a modification, but provides no deeper behavioral context beyond the property names.

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 definition is a single front-loaded sentence with no filler. Every word contributes to explaining the tool’s action and the property categories it affects.

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 six-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits required parameters, audit-log context, permission requirements, and the distinction between clearing tags and omitting them, leaving important invocation details to the schema.

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 100%, so the schema already documents each parameter, including required postId and the tag-clearing behavior. The description names the main property groups (lock, archive, pin, tags) but adds no syntax or format details beyond what the schema provides. A baseline 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 gives a specific verb and resource: modify forum post properties. It enumerates the modifiable properties (lock, archive, pin, tags), which distinguishes it from create_forum_post and list_forum_posts. It does not explicitly differentiate from similarly named siblings such as modify_thread or pin_message, so it falls short of a 5.

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 states only what the tool does, with no guidance on when to use it versus alternatives. There is no mention of prerequisites, when not to use it, or which sibling to prefer for related operations.

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