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

No annotations are provided, so the description carries the full behavioral burden. It discloses the internal pipeline (crawl, dedupe/sort, generate Chinese daily report, push to configured webhook), which tells the agent this is a net mutating/side-effecting operation. It does not state idempotency, rate limits, failure behavior, or whether the dedupe state persists between runs.

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?

A single front-loaded sentence with zero waste, describing purpose and pipeline in one compact clause. No repetition or padding.

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 zero-required-parameter, side-effecting action tool with no output schema, the description is adequate but omits important operational context: what a returned 日报 looks like, webhook failure handling, and interaction with reset_seen or push_status. It is usable but not complete.

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 schema already documents all four parameters (top, push, hours, min_heat) in Chinese. The description does not add syntax, format, or edge-case semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb (执行一轮监控扫描) and resource (监控账号新帖), then enumerates the pipeline stages: 抓取、去重排序、生成日报、推送 webhook. This is clearly distinct from siblings like push_status or reset_seen.

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 when-to-use or when-not-to-use guidance relative to alternatives. The description implies an immediate ad-hoc scan versus scheduled monitoring, but does not state this or name any sibling tool as a non-overlapping alternative.

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