moltbook_comments_list

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

With no annotations, the description carries the full burden of disclosing behavior, but it simply states 'List comments for post.' It does not mention ordering, pagination, permissions, or any side effects. While 'list' implies read-only, it fails to provide any additional behavioral context beyond the basic action.

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 at four words, with no wasted words. It is front-loaded with the primary action. However, it is slightly under-specified, lacking any parameter or usage context, which prevents a perfect score.

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 two parameters, an enum, and no output schema or annotations, the description is minimally complete. It covers the core action but omits any mention of sorting, result format, or additional behavior. A more complete description would include at least one sentence about the sort options or expected output.

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 mentions 'for post,' which loosely maps to the post_id parameter, but it does not explain the sort parameter or its default value. With 0% schema description coverage, the description was expected to compensate, but it adds minimal meaning beyond what the schema already provides.

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 uses a specific verb 'list' and resource 'comments for post,' making the primary action clear. It distinguishes this tool from siblings like post_get and posts_list by indicating it specifically retrieves comments rather than posts or other entities. However, it lacks any explicit comparison to similar tools, so not a full 5.

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 gives no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or context for choosing it over other list tools. This is a clear gap since no alternatives or conditions are provided.

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