search_reddit

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

With no annotations, the description carries the full burden and does well: it discloses search-matching behavior, describes the return shape (posts with id + subreddit), and adds an important prompt-injection warning that returned titles/bodies/comments are UNTRUSTED user text. It stops short of noting rate limits, auth requirements, or pagination behavior for the private instance.

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 tight sentences, front-loaded with the core action and the highest-risk guidance (query shape) before the alternative-tool routing and the untrusted-content warning. Every sentence carries distinct information.

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 5-parameter search tool with no annotations and no output schema, the description covers what the tool returns, how to phrase queries, when to use a sibling instead, and the trust level of returned content. Minor gaps remain around result volume/pagination and any access constraints on the private instance.

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 sort, time, limit, query, and subreddit are already documented in the schema. The description reinforces the query semantics with a rationale (exact-ish term matching) but adds no syntax or format detail for the other four parameters, so the baseline 3 applies.

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 (Search) and resource (Reddit posts) with the mechanism (private Redlib instance). It also explicitly distinguishes itself from siblings, naming get_subreddit_posts as the alternative for 'best/recent posts about X' and get_post as the follow-up tool.

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?

Gives explicit query-construction guidance ('use SHORT keyword queries (2-5 words)', search is 'exact-ish term matching, NOT natural language') and an explicit routing rule to a named alternative for a specific intent. Nothing is left to inference.

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