search_posts

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

With no annotations provided, the description carries full behavioral burden. It mentions 'public posts' and 'approved subreddit' as constraints, but does not disclose rate limits, authentication needs, pagination, sorting behavior, or what constitutes 'approved'.

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 description is a single efficient sentence with no fluff. It front-loads the core purpose directly. However, it is under-specified, but that is a completeness issue rather than a conciseness issue.

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?

Despite being a search tool with 5 parameters, enums, and no output schema or annotations, the description offers only a terse purpose statement and scope constraint. It does not cover return format, parameter semantics, or operational details, making it incomplete for reliable use.

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%, so the description must compensate for parameter meaning. It implicitly hints at 'query' and 'subreddit' by saying 'search posts inside a subreddit', but provides no details about sort, limit, or time_filter, leaving most parameters unexplained.

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 uses a specific verb 'Search' and clearly specifies the resource ('public posts') and scope ('inside one approved subreddit'). It distinguishes itself from siblings (list_subreddit, get_post, get_comments) which serve different purposes.

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?

No explicit guidance on when to use this tool versus alternatives, nor any exclusions. The phrase 'approved subreddit' implies a prerequisite, but the description does not elaborate on when to choose search_posts over list_subreddit or get_post.

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