moltbook_subscribe

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It does not mention authentication requirements, idempotency, side effects, or what happens if already subscribed. For a mutation tool, this is a critical omission.

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 concise with only three words, but this is under-specification rather than appropriate conciseness. It contains no sentences and provides no structure or explanations, earning a low score for failing to deliver essential information.

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 tool with no annotations, no output schema, and a single undocumented parameter, the description is severely incomplete. It does not explain how to identify the submolt, what a successful subscription looks like, or any error conditions. The agent cannot confidently use this tool based on the current information.

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 schema has one parameter 'name' with no description and 0% coverage. The description 'Subscribe to submolt' does not explicitly state what the 'name' parameter refers to or its format. The agent must infer that 'name' is the submolt's name, which is not guaranteed and not helpful for a correct invocation.

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 'Subscribe to submolt' clearly identifies the action (subscribe) and the target resource (submolt). It distinguishes from sibling tools like moltbook_unsubscribe and moltbook_follow. However, it does not explain what a submolt is or what subscribing entails, so it falls just short of a 5.

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?

There is absolutely no guidance on when to use this tool versus alternatives. No mention of prerequisites, typical use cases, or when not to use it. The description is purely a bare action statement with no context.

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