moltbook_feed

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

No annotations are provided, and the description only says 'Alias for moltbook_posts_list.' It does not disclose whether the tool is read-only, whether authentication is required, whether there are rate limits, or any side effects. The description fails to carry the burden of behavioral disclosure.

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, which is superficially concise, but it is under-specified. It lacks essential information about the tool's function, behavior, or parameters, making the brevity a deficiency rather than a strength.

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 tool with 3 parameters, no output schema, and no annotations, the description is completely inadequate. It provides no context about what the tool returns, how parameters affect behavior, or edge cases. The agent cannot effectively invoke or interpret results based on this description alone.

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 input schema defines three parameters (sort, limit, submolt) with no descriptions, and schema description coverage is 0%. The description does not mention any parameter, nor does it clarify their meaning or relationships. It adds no value beyond the schema's structural definitions.

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 states 'Alias for moltbook_posts_list,' implying it performs the same function as that tool, but it never explicitly states what the tool does (e.g., list posts). This is not a complete tautology but relies on the reader knowing the target tool, leaving the purpose vague.

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?

There is no guidance on when to use this tool versus any alternatives. It does not explain why an agent should choose 'moltbook_feed' over 'moltbook_posts_list' or any other sibling, nor does it mention any conditions or exclusions.

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