Get detailed Reddit posts

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds genuinely useful operational context (Reddit is unavailable, error_code=reddit_unavailable), but omits behavioral details like pagination, result limits, or what an empty result means.

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?

Three short sentences, front-loaded with the core purpose before the caveat. The availability sentence and the publish-target warning overlap slightly but both carry actionable instruction rather than 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?

An output schema exists, so return values needn't be explained, and the read-only profile is covered by annotations. The main residual gap is the undocumented `limit` parameter; otherwise the definition is sufficient to call the tool correctly and to know it currently fails.

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 50%: `profile` is documented in the schema and echoed in the description, but `limit` (1–200) is unexplained in both schema and description—no default, no pagination semantics. With partial coverage, the description does not fully compensate, keeping this at baseline 3.

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?

States a specific verb and resource ('Recent Reddit posts published from a profile') plus the payload shape (subreddit, flair, score metadata). It does not name any sibling or contrast with alternatives, but no sibling in the list fetches Reddit posts, so differentiation is implicit.

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 a when-not ('Do not use reddit as a publish target') but that constraint is about publishing, not about invoking this read tool, and no alternative read tool or fallback is suggested. Usage context for fetching posts is only implied.

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