Submit text post

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

With no annotations provided, the description reveals the dry run behavior, which is important for safety. But it lacks other behavioral details such as error handling, rate limits, or side effects, which are necessary for a mutating tool.

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 concise with two sentences, front-loading the key action and then providing a critical safety note. Every sentence serves a purpose with no fluff.

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 has 8 parameters, 3 required, no output schema, and no annotations, the description is insufficient. It omits parameter meanings, return values, and error conditions, leaving the agent underinformed for correct invocation.

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 explanation of the input parameters beyond the schema. Schema description coverage is only 13% (one parameter described), so the description should compensate but does not. The dry run note is about an environment variable, not a parameter.

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 the tool 'Publishes a Reddit text post,' which is a specific verb and resource. It distinguishes itself from sibling tools like preview_text_post and search_subreddits by indicating actual submission.

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 mentions the DRY_RUN environment variable and advises setting it false only after testing, which gives some guidance on when to use the tool. However, it does not provide when-not-to-use conditions or mention alternative tools like for link posts.

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