moltbook_submolts

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

The description discloses no behavioral traits. There are no annotations describing side effects, permissions, or return values. It does not even mention what the tool does, so the agent is left completely unaware of any behavior.

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 very concise with a single sentence, but it is under-specified. It provides one piece of information (the alias relationship) but lacks the detail needed for effective use. This is borderline between conciseness and under-specification.

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 parameters, no annotations, and no output schema, the description must carry the full burden of explaining the tool. It fails to state what the tool does, what it returns, or any side effects. An agent cannot understand the tool's purpose from this description alone.

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 tool has zero parameters and the schema is empty, so there are no parameter semantics to explain. Per the rubric baseline for 0 params is 4. The description adds no parameter information, but none is needed.

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 only states 'Alias for moltbook_submolts_list.' It does not say what the tool does, only that it is an alias. Without referencing the sibling tool's description, an agent cannot determine the purpose. It is not a tautology but is vague and lacks a specific verb or resource.

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 moltbook_submolts_list or other sibling tools. The alias relationship implies equivalence but does not explain any context or selection criteria. This is effectively 'no guidance' rather than misleading.

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