create_post

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

Annotations already declare non-idempotent and openWorld, but description adds critical context: requires REDDIT_USERNAME/PASSWORD, is mutating (confirmed by readOnlyHint=false), and returns id/URL. Warns of account bans without safe mode, which is valuable beyond annotations.

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?

Well-structured with clear sentences, but somewhat long. Front-loaded with action and key caveats. The warning about spam detection is useful but could be shortened without losing value.

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 mutating, non-idempotent tool with no output schema, the description covers prerequisites, return values, and risks. It compensates for missing output schema by stating the returned id and URL. Adequately complete for an agent to use correctly.

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%, so baseline is 3. Description adds meaning by linking content to is_self, explaining flair requirements, and mentioning that title cannot be edited later. Does not repeat every parameter but reinforces key usage constraints.

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?

Clearly states it creates a text or link post in a subreddit, with explicit verb and resource. Distinguishes from siblings like delete_post and edit_post by describing the publish action and the distinction between self/link posts.

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?

Provides explicit when-to-use guidance: check get_subreddit_rules and get_post_flairs first for required flairs or content restrictions. Also warns against rapid posting due to spam detection, aligning with the openWorldHint and non-idempotent annotations.

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