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

Annotations already declare readOnly=false, idempotent=false, openWorld=true, destructive=false, so the safety profile is covered. The description adds real behavioral context beyond that: it returns a job id (asynchronous), results appear in the feed/opportunities views within a minute, and it duplicates scheduled scan work. It does not explicitly restate non-idempotency or note any rate/credit cost, so it is not a 5.

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?

Front-loaded purpose sentence, then usage gating, then outcome, then an Args block. Every sentence carries information; nothing is redundant with the name or title.

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?

No output schema exists, and the description correctly states the return value (a job id) plus where results land and roughly how long they take. That covers what an agent needs to call and follow up. It stops short of stating any cost, credit usage, or failure behavior for a non-idempotent trigger.

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 coverage is 50%. The description documents brand_id semantically ('The brand to scan (required)'), which adds a little value over the bare schema, but it is silent on the user_intent parameter, leaving that to the schema's own description. Baseline 3 is appropriate given partial coverage.

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?

Specific verb+resource: 'Trigger an on-demand Reddit scan for the brand'. It clearly distinguishes itself from the read-side sibling get_reddit and from the manage_reddit_* configuration tools by framing this as a one-off execution rather than a configuration or retrieval call.

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?

Explicit when-to-use and when-not-to-use: it states most brands already run a daily scheduled scan and instructs to use this 'only when you want results faster', naming concrete triggers (adding a subreddit or trigger). That is a full routing rule an agent can apply without inference.

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