verify_moltbook_post

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

Discloses that submission is a write operation with earning points, daily cap, and 7-day lock-in. No annotations provided, so description carries the full burden; it is mostly sufficient. However, does not specify required permissions or reversibility.

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?

Single sentence, 14 words, front-loaded with action, parenthetical adds key constraints. No redundant information.

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?

With one simple parameter and no output schema, description covers action and limits. Missing details: what 'verification' entails, return value, and prerequisites (e.g., linked Moltbook account). Still adequate for basic usage.

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 coverage is 100% with param description 'Post UUID or URL'. Description adds no additional parameter meaning beyond the schema, earning baseline 3.

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?

Description clearly states action 'Submit a Moltbook post for verification' and adds distinct context (earns points, daily cap, lock-in). Distinguishes from sibling 'verify_moltbook' which likely handles account-level verification.

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?

Implies usage through 'max 3/day, 7-day lock-in' but does not explicitly contrast with alternative verification tools like verify_moltbook, verify_social_tweet, or verify_twitter. Agent must infer when to use this specific tool.

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