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

Beyond the annotations (readOnlyHint false, idempotentHint false), the description discloses critical behaviors: it publishes immediately and publicly under the user's username, warns about Reddit's harsh treatment of undisclosed self-promotion, and explains that flair-required subreddits are detected pre-post with error listing valid flairs. This adds substantial context beyond the annotations, which only indicate it is a non-read, non-idempotent operation. No contradiction with 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?

The description is well-structured and front-loaded: it starts with the action, then covers confirmation, policy warning, one-subreddit rule, flair handling, and connection requirement. Each sentence adds value, though it is somewhat lengthy. The warning paragraph could be condensed, but it is not redundant. Overall, it is efficient for the complexity.

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 complex mutating tool with 13 parameters and no output schema, the description covers all essential operational context: the need for user confirmation, the one-subreddit limit, the self-promotion risk, flair handling, and connection requirement. It does not need to describe return values since no output schema exists. It is sufficient for an agent to call correctly and safely.

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 85%, so the schema already documents most parameters well. The description adds minor value: it specifies that imageUrl should be a 'Hermoso render URL' (also in schema) and mentions flairId handling in the error case, but these are not substantial. It does not explain the 'hook' or 'subject' parameters beyond what the schema already states. Baseline 3 is appropriate given high schema coverage.

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 action: 'Submit a post to ONE named subreddit' and enumerates the three post types (text, link, image). It distinguishes itself from sibling tools by specifying the Reddit context and the 'ONE subreddit' constraint, which is not present in other posting tools. The verb 'submit' and resource 'subreddit' are 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?

The description provides strong when-not constraints: explicitly says to post to ONE subreddit and to refuse broadcast requests, and requires explicit user confirmation before calling. It also mentions the need for Reddit to be connected. However, it does not explicitly name alternative tools (e.g., 'use post_to_linkedin for LinkedIn'), so it lacks explicit alternative routing, but the context makes it clear when to use this tool.

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