create_post

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

With zero annotations, the description carries the full behavioral burden, yet it only says what post types exist. It does not disclose whether the post publishes immediately (draft vs scheduled), what permissions are required, or what happens to category-specific fields for unrelated categories – critical for a 17-parameter mutation 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 short sentences, front-loaded with the core action, with no filler. The second sentence earns a bit of place by enumerating supported content types, though it partly restates the category enum.

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 17-parameter tool with no annotations and no output schema, the description is too thin. It omits how the many category-specific fields interact (Launches vs Videos vs Articles), draft/scheduling semantics, and any return or confirmation behavior.

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 the schema already documents all 17 parameters including the category enum and per-category fields. The description's mention of Articles/Tutorials/Launches/Videos loosely maps to the category enum but adds no syntax or constraint detail beyond it. Baseline 3 applies.

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?

States a specific verb+resource ('Create a new post on CoderLegion'), clearly distinct from siblings like edit_post and get_post. The second sentence names the supported post categories, which helps scope the tool, but there is no explicit contrast with any sibling beyond the verb itself.

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?

No guidance on when to use this vs edit_post or list_posts, nor any mention of prerequisites (auth, category selection). Usage is only inferable from the bare verb 'create'.

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