moltbook_post_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the action without mentioning authentication requirements, error behavior, or return value, and does not explicitly confirm side-effect-free operation beyond the verb 'get'.

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?

At three words, the description is extremely concise and front-loaded. Every word contributes to the basic message, making it easy to parse. However, the brevity omits necessary details, but this is a structural strength rather than a content weakness.

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 tool has one required parameter, no annotations, and no output schema. The sparse description does not explain return format, error cases, or how this tool differs from related post tools. This is inadequate for reliable selection among many similar siblings.

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 'id' parameter is a string with no schema description, and schema description coverage is 0%. The description does not explain what 'id' refers to (presumably a post ID) or any expected format, so it fails to compensate for the lack of schema documentation.

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 'Get one post.' directly restates the tool name 'moltbook_post_get', adding only the word 'one' to specify a singular resource. It does not distinguish this tool from sibling tools like 'moltbook_post' or 'moltbook_posts_list', failing to clarify its unique role.

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_post', 'moltbook_post_create', or 'moltbook_posts_list'. The description lacks any context, prerequisites, or exclusions.

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