moltbook_raw_request

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

With no annotations, the description must disclose behavioral characteristics, but it only mentions the allowlist constraint. It doesn't state whether the tool can perform destructive operations, what authentication is required, or what happens on disallowed paths. The lack of detail is a significant gap for a tool that presumably can issue arbitrary HTTP requests.

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 at the expense of essential detail. It is under-specified rather than appropriately concise. Every dimension suffers from the lack of content.

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 four parameters including nested objects and no output schema, this description is wholly inadequate. It fails to explain request construction, response format, or constraints beyond the vague allowlist note. The tool is a general-purpose raw request, so more context is needed even if siblings exist.

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 description provides no information about the parameters (path, method, body, query), even though the schema has zero description coverage. The schema itself shows names and types but not their meaning in the context of a raw request. The description must compensate but doesn't, leaving the agent without guidance on how to construct valid requests.

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 clearly states this tool makes raw API requests, which establishes its function as a low-level HTTP client. The mention of allowlisted paths adds some scope, but it doesn't specify which paths are allowed or what the tool is actually for beyond that. It distinguishes itself from sibling tools by being generic rather than endpoint-specific.

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 raw request tool versus the many specific sibling tools. No context about scenarios requiring the raw endpoint, nor warnings against using it. The description is entirely silent on usage context.

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