reddit_submit_post

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

No annotations are provided, so the description alone must disclose the behavior. It correctly implies a write/mutation operation, but it does not mention permanence, visibility, authentication requirements, rate limits, or side effects. For a creation tool this is a meaningful gap.

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 entire description is one lean, front-loaded sentence that conveys the core action, supported formats, and valid targets. There is no redundancy or filler.

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 seven parameters, the description is somewhat thin. It covers the essential 'what' and 'where', but omits practical context such as authentication, post visibility, and response behavior, which an agent would benefit from knowing before invoking a mutating Reddit API call.

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 description coverage is 71%, so most parameters are already documented. The description adds minimal extra value by framing 'body' as markdown and 'url' as links, but it does not clarify exclusivity or parameter combinations beyond what the schema already implies.

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 uses a specific verb ('Publish') and resource ('post'), and clearly specifies the allowed destinations ('any subreddit or own profile') and post types ('text/markdown or link'). This unambiguously distinguishes it from sibling tools like reddit_submit_comment.

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 gives clear context for when to use this tool: whenever a new post needs to be published to a subreddit or personal profile. It does not explicitly name alternatives or exclusions, but the intended use case is obvious from the phrasing and the sibling tool names.

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