moltbook_pin_post

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the authorization requirement (moderator-only), but says nothing about what pinning actually changes (feed ordering, single-pin replacement), whether it is reversible, or how permission failures surface.

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?

A single sentence with zero filler; the action is front-loaded and the permission qualifier is appended where it is immediately visible. Nothing in it fails to earn its place.

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?

For a one-parameter mutation with no output schema, the description covers purpose and permission but leaves pinning semantics and failure behavior unspecified. Adequate to invoke correctly, but thin for a state-changing moderation 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?

Only one parameter and schema description coverage is 100%, so the schema already documents postId fully. The description adds no format, scoping, or lookup detail beyond what the schema provides, making the baseline 3 the correct ceiling here.

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?

States a specific verb and resource ("Pin a post") plus scope ("in a submolt"), so an agent can immediately tell it apart from moltbook_unpin_post, moltbook_post, and moltbook_delete_post. It stops short of explicitly naming the sibling it complements, so it is clear but not maximally differentiated.

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?

"Moderator only" is a real precondition that tells the agent who may invoke it, which is more than nothing. However, there is no guidance on when to pin versus other moderation actions, no mention of what happens if the post is already pinned, and no explicit exclusion criteria.

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