create_post

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states only the creation action and a tag-format detail, with no mention of return value, permission requirements, side effects, or behavior when tags are invalid. For a mutating tool with zero annotation coverage, this is a significant gap.

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 short sentences with the purpose front-loaded and zero filler. The second sentence earns its place by clarifying tag semantics. The only reason not to give a 5 is that the brevity comes at the cost of omitting useful behavioral context, though that is a completeness concern rather than a structure flaw.

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 mutation tool with 4 parameters, no annotations, and no output schema, the description is not complete enough. It doesn't describe what a successful create returns (e.g., a post ID), any preconditions on forum_id, or how missing tags are handled at creation time.

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. The clause '`tags` are tag names or IDs' adds real meaning beyond the schema's bare 'array of string or null' type. However, forum_id, title, and content receive no elaboration, so compensation is only partial.

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 'Create a forum post' pairs a specific verb (create) with a specific resource (forum post), which cleanly distinguishes it from siblings like read_post, reply_post, list_tags, and close_post. The purpose is unambiguous and immediately actionable for an agent.

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 offers no guidance on when to use this tool versus alternatives such as reply_post or add_tags, and no exclusions or prerequisites are mentioned. It doesn't say how to obtain a valid forum_id or whether tags must pre-exist, leaving selection and preconditions to inference.

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