moltbook_post

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says it is an alias and does not explain any behavior, side effects, permissions, or return values, leaving the agent completely 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 short, but this is under-specification rather than effective conciseness. A single clause that reveals almost nothing about the tool's operation does not earn credit for being concise.

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?

The description is completely inadequate for a tool with a required parameter and no output schema. The alias pointer might be acceptable if the target were well-documented, but the description must be self-contained for the agent to use 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?

The single parameter 'id' is undocumented in both the schema and the description. With 0% schema description coverage, the description must explain what 'id' refers to, but it does not mention it at all.

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 states 'Alias for moltbook_post_get,' which identifies a relationship to another tool but does not state what the tool actually does. It lacks a specific verb and resource, leaving the function opaque unless the agent already knows moltbook_post_get.

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 alias versus moltbook_post_get or any other sibling tool. The description is purely definitional and offers no contextual or preferential advice.

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