moltbook_posts_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. The verb 'List' implies a read-only operation, but no other behavioral traits are disclosed, such as pagination, authentication requirements, rate limits, or what happens with invalid inputs.

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 a single short sentence with no filler words, making it quick to read. However, it is so terse that it omits important context, especially given the tool's parameter count and the number of sibling tools. It is concise but not appropriately sized for the complexity.

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?

The description is incomplete for a tool with no output schema, no annotations, and 3 parameters. It does not explain what 'posts' are, how 'submolt' filtering works, default behavior, or the structure of the response. With many sibling tools, more context is needed to avoid confusion.

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 mentions 'sort' and 'submolt' as factors but does not explain their allowed values or behavior, and it omits the 'limit' parameter entirely. The enum values in the schema are self-explanatory, but the lack of detail on parameter semantics leaves gaps.

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 ('List') and resource ('posts'), and adds the qualifier 'by sort/submolt' which gives some context. However, it does not distinguish this from sibling tools like moltbook_feed or moltbook_feed_personal, which may also list posts, so it lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or any comparison to related tools such as moltbook_feed or moltbook_search.

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