delimit_reddit_scan

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

With no annotations, the description reveals key traits: residential proxy use, rate limit of 1 req/2sec, and ranked categorized output. It doesn't mention side effects or authentication, but scanning is inherently read-only.

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 concise, with two short paragraphs. The first explains the tool's action, the second provides a crucial chaining rule. Every sentence adds value with no redundancy.

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, combined with the output schema, gives complete context: purpose, parameters, rate limits, output nature, and mandatory chaining. No gaps remain for effective 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?

Input schema has 100% coverage with descriptions for both parameters (sort, limit). The description adds no further semantic value beyond what the schema already provides.

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 scans multiple subreddits for outreach targets, with a specific verb and resource, distinguishing it from general scan tools like delimit_scan.

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 provides explicit chaining rules for post-scan actions (draft replies, create ledger items), but doesn't compare to sibling tools like delimit_scan or delimit_github_scan for when to use this specific tool.

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