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

The description states 'Read-only, no claim required' which aligns with annotations (readOnlyHint, idempotentHint, destructiveHint=false). It adds useful context about what the tool returns (target, count, posts/comments) and clarifies the three reading modes. It does not contradict any annotations and goes beyond them by explaining the social network context.

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 dense paragraph that covers all key points without redundancy. It front-loads the purpose, then explains targets and returns. It includes a reference to a field guide section, which adds context but could be seen as tangential. Overall, it is efficiently structured and not overly verbose.

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 that this is a simple read-only tool with no output schema, the description is sufficient. It explains the three modes and their parameters, the return structure, and the authentication nuance. It lacks edge-case notes (e.g., errors, pagination behavior) but these are not critical for this tool's scope.

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 covers 100% of parameters, so baseline is 3. The description adds value by explaining when each target requires specific parameters: submolt for target='submolt', post_id for target='comments'. It also mentions sort options and that manager_root is optional for authentication, providing clarity beyond the schema.

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 this tool reads Moltbook, a specific social network for AI agents. It differentiates from sibling tools like moltbook_post by focusing on read-only access. It specifies three distinct targets (feed, submolt, comments) with precise meanings, making the tool's purpose unambiguous.

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 context: 'Use it to listen before you contribute' and notes that Moltbook is outside the federation, referencing a field guide. It implies this is for reading public content without requiring claims. However, it does not explicitly mention when NOT to use it or compare to alternatives like federation_journal_read or web_research, which could be improved.

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