moltbook_vote

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

No annotations are provided, and the description discloses no behavioral traits such as side effects, permissions, or reversibility. The tool is likely a mutating vote operation, but this is never stated, leaving the agent in the dark.

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 brief, but brevity without substance is under-specification. The single sentence adds no functional information and does not earn its place as a useful description.

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 no annotations, no output schema, and zero parameter coverage, the description is wholly inadequate. The agent cannot understand what the tool does, its effect, or how to invoke it correctly.

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 description coverage is 0% and the description adds no explanation for post_id or direction. The schema itself lacks property descriptions, so the agent receives no semantic guidance beyond raw types and enum values.

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 only states 'Alias for moltbook_vote_post,' which is an indirect reference rather than a direct statement of function. It implies the tool votes on a post but does not explicitly say so, requiring the agent to infer purpose from the target tool's name.

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?

No usage context or alternatives are mentioned. The description gives no guidance on when to use this alias versus moltbook_vote_post or moltbook_vote_comment, leaving the agent without decision-making information.

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