zernio_reddit_submit_post

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 only states the action of submitting a post but does not disclose side effects, rate limits, permissions needed, validation rules (e.g., one of content or url must be provided for a valid post), error handling, or return 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 a single short sentence, which is front-loaded but under-specified for a tool with 5 parameters and no annotations. It sacrifices completeness for brevity, lacking critical context about post types and prerequisites.

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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is incomplete. It does not explain the behavior for different post types, mention validation, or provide hints about the return value. More context is needed to fully understand tool usage, especially when compared to sibling posting 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?

Schema coverage is 100% with all parameters described. The description adds no additional meaning beyond what is in the schema. It does not clarify the difference between content (text post) and url (link post) or that one of them is typically required for a valid post. Baseline score of 3 is appropriate.

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 'Submit a new post to a Reddit subreddit from a connected account,' specifying the verb (submit), resource (post), platform (Reddit), and prerequisite (connected account). It distinguishes itself from sibling tools like zernio_create_post (which may target other platforms) and other Reddit tools like zernio_reddit_upvote.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it or compare it with other posting tools (e.g., zernio_create_post) or Reddit-specific tools. The mention of 'connected account' is a prerequisite but lacks clarity on how to ensure connection.

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