reddit_stats

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

With no annotations, the description fully carries the burden. It describes the return values in detail, indicating a read-only operation. However, it lacks mention of performance or rate limits, which would be beneficial for an agent.

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?

Two sentences with no wasted words. The purpose is stated first, followed by a list of outputs. Efficient and well-structured.

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 stats retrieval tool with one optional parameter and an output schema, the description provides sufficient detail on what is returned and the scope. Missing minor details like authentication or profile existence checks, but acceptable.

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 covers 0% of parameter meaning. The description adds value by stating the profile parameter optionally scopes the stats, but does not explain its format or behavior beyond that.

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 returns summary stats for the store, optionally scoped to a profile. It lists specific outputs (totals, split, breakdown, patterns, date range), distinguishing it from sibling tools that focus on querying or exporting data.

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 optional scoping to a profile, implying when to use the parameter, but does not explicitly state when to use this tool versus siblings like reddit_query or reddit_search.

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