reddit_daily_digest

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

The description goes well beyond the readOnlyHint/openWorldHint/destructiveHint annotations. It discloses the retention cleanup side effect, states that no Reddit write code exists, clarifies that the server is read-only, and notes that it returns only URLs to open, never a ready-to-post body. This is rich, non-redundant behavioral context.

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 core purpose and constraints are front-loaded, and the read-only and policy guidance are relevant for agent behavior. Some redundancy exists ('no such code exists', 'never posts anything') and 'The main tool' is filler, but the description is still efficiently organized and not bloated.

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?

The description covers return shape, side effects, and constraints, and the tool has an output schema plus optional parameters with defaults. The main gaps are the complete lack of parameter semantics and no routing guidance relative to sibling tools. This is a meaningful hole for a main entry-point tool, but not fatal because it can be invoked with defaults 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 0%, and the description does not mention days, max_replies, or max_opportunities at all. The phrase 'one day's work queue' may even obscure the configurable days parameter. Since the schema provides no parameter documentation and the description does not compensate, an agent has no guidance on how these parameters affect the output.

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 that the tool produces a daily work queue and enumerates its contents: new replies, ranked contribution places, what the user can say, verification needs, rule caveats, and reminders. It explicitly says it never returns a ready-to-post comment body and never posts anything, which distinguishes it from posting or content-generation tools.

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?

It implies this is the main daily entry point ('The main tool', 'Produces one day's work queue'), and it sets expectations that the user performs Reddit actions manually. However, it does not explicitly say when to prefer this over siblings like reddit_get_replies_to_me or reddit_find_opportunities, nor does it state when not to use it.

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