moltbook_vote_post

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Vote on post' adds no information beyond the tool name—no effects of voting, idempotency, authentication requirements, rate limits, or reversible actions. This is essentially a tautology.

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 short, but it is under-specified rather than appropriately concise. It does not earn its place by providing useful information—it just repeats the tool name. A concise description should still be informative, which this is not.

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 a minimal description, the tool is completely incomplete. The agent has no information about return values, side effects, or the broader context of voting on a post. This is inadequate for a tool with two parameters and a mutation action.

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 does not mention either `post_id` or `direction`. The schema already provides basic type/enum info, but the description adds no meaning, leaving the agent with no additional context about what these parameters represent or how they behave.

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 action ('Vote') and resource ('post'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like moltbook_vote_comment or moltbook_vote, so it lacks explicit sibling distinction.

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 guidance is provided on when to use this tool versus alternatives such as moltbook_vote_comment or moltbook_vote. The description gives no context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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