moltbook_post_create

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 states 'Create a new post' which implies a write/mutation operation, but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what happens on success (e.g., returns a post ID). For a creation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise with a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it easy to parse quickly. It's appropriately sized for a simple creation tool.

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?

Given the complexity of a post-creation tool with no annotations, 4 parameters (only 50% documented in schema), no output schema, and multiple sibling tools, the description is insufficient. It doesn't explain return values, error conditions, or how it fits into the broader Moltbook ecosystem. For a mutation tool, more context is needed to ensure safe and correct usage.

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?

The description adds no parameter information beyond what the schema provides. With 50% schema description coverage (only 'content' and 'url' have descriptions), the description doesn't compensate for undocumented parameters like 'title' or 'submolt'. However, since the schema covers half the parameters and the tool has 4 parameters, the baseline is 3, as the description doesn't degrade but also doesn't enhance parameter understanding.

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 clearly states the action ('Create') and resource ('new post on Moltbook'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'moltbook_post' (which might be for reading/updating posts) or explain what distinguishes a 'post' from other content types like 'comment' or 'feed' entries.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), when not to use it, or how it relates to sibling tools like 'moltbook_post' (which might handle post retrieval) or 'moltbook_comment' (for adding comments). The description is purely functional without contextual advice.

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