reddit_request

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

The description adds important behavioral context beyond the readOnlyHint annotation: responses are raw and unshaped, listings are roughly ten times larger, writes are disabled by default, and POST can be enabled via an environment variable. This is exactly the kind of non-obvious runtime behavior an agent needs to know. The mention of POST is inconsistent with the schema's method enum, but not with the 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?

Four sentences, each earning its place: purpose, path example, response-size warning, and write policy. The most important routing information is front-loaded.

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 passthrough tool with no output schema, it covers the key risks: raw response size, write restrictions, and path format. However, the description's claim that POST can be enabled conflicts with the schema's method enum, which only permits GET; this could confuse an agent trying to invoke the advertised POST capability.

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 100%, so the baseline is 3. The description's example path and the 'keep limit small' warning add some practical context, but it does not meaningfully enhance the parameter-level semantics already present in the schema.

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 opens with a clear verb and resource: 'Call any Reddit API endpoint directly, for the many endpoints this server does not wrap.' This immediately distinguishes it from the wrapped sibling tools and explains its role as a passthrough for the rest of the Reddit API.

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 clearly states when to use it — for endpoints the server does not wrap — and includes operational guidance about raw responses and write restrictions. It does not explicitly name alternatives, but the phrase 'this server does not wrap' implies the sibling tools should be preferred for covered endpoints.

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