moltbook_submolt_get

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 behavioral disclosure. It does not state whether this is a read-only operation, whether authentication is required, or what the response contains. The single phrase offers no transparency into side effects, rate limits, or error 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 extremely short, but this is under-specification, not appropriate conciseness. A single short phrase does not earn its place because it fails to convey essential information. It is not front-loaded with useful details; it is simply insufficient.

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 one parameter, no output schema, and no annotations, the description should at least explain what a submolt is and what the tool returns. It does neither, making it wholly inadequate for an agent to select and invoke the tool correctly, especially given the numerous sibling tools.

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 0% description coverage and lists a single required 'name' parameter with only a string type. The description does not explain what 'name' refers to (e.g., submolt ID, slug, display name) or provide any context. The agent is left to guess the parameter's meaning.

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 submolt' states a verb and resource but provides no scope or distinction from sibling tools like submolts_list or submolt_create. It is barely more informative than the tool name itself and fails to clarify what a submolt is or what 'get' returns.

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 no guidance on when to use this tool versus alternatives. The description does not mention when to prefer this over submolts_list or other retrieval tools, nor does it state any prerequisites or exclusions.

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