moltbook_thread_diff

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 describes the core behavior (fetching posts with new activity and reporting delta counts) but doesn't mention important details like whether this requires authentication, rate limits, how 'last view' is determined, or what happens if no new comments exist. It adds some context about what gets returned but lacks comprehensive behavioral traits.

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 perfectly structured and concise: a clear purpose statement, a usage context sentence, and well-organized parameter/return sections. Every sentence earns its place with no wasted words, and the information is front-loaded with the core functionality stated first.

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 tool's moderate complexity (tracking new comments across posts), no annotations, no output schema, and 1 parameter with good description coverage, the description is adequate but has gaps. It explains what the tool does and the parameter, but doesn't describe the return format in detail (what fields posts include, how delta counts are structured) or address behavioral aspects like authentication needs.

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 significant meaning beyond the input schema, which has 0% description coverage. It explains the 'scope' parameter's two possible values ('engaged' and 'all') and what they mean, which the schema only lists as a string type with a default. Since schema coverage is low, the description effectively compensates by providing the necessary parameter semantics.

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 tool's purpose with specific verbs ('Check tracked posts', 'Fetches posts', 'reports any with new activity') and distinguishes it from siblings by focusing on detecting new comments in previously engaged posts. It specifies the exact resource (posts with new comments) and differentiates from general feed or notification tools.

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 clear context for when to use this tool ('Useful for catching replies to your comments or posts'), but doesn't explicitly state when not to use it or name specific alternatives among the sibling tools. It implies usage for monitoring engagement rather than general browsing or posting.

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