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

Annotations already declare readOnlyHint and openWorldHint, and the description goes well beyond that by disclosing billing behavior (success deducts 20 points, failures are free), the absence of date filtering and the unknown statistics cutoff, and interpretive limits (store visits ≠ orders, cost estimates ≠ actual cost/ROI, the output echoes the scope but cannot be mixed). That is unusually rich disclosure. One point is withheld because the response shape is only summarized ('返回业务字段和 points') rather than characterized, even though an output schema exists.

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 long but front-loaded, moving from purpose to routing, then scope semantics, then caveats, then billing. Each paragraph carries distinct information, though the daily/cooperation explanation is repeated in substance between the body and the note_scope schema description, and the wording is dense enough that some caveats need a second read.

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?

An output schema exists, so return values need not be documented, and the description still notes the points/business-field response and the billing charge. For a two-parameter, read-only overview tool it covers selection criteria, interpretation caveats, and cost, leaving nothing material an agent needs to call it correctly.

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 baseline would be 3. The description nevertheless adds meaning beyond the schema for note_scope by warning that daily here means the content family, not per-day aggregation, and by cautioning that the chosen scope does not uniformly filter every field, so note_count must not be read as a scoped note total. That is genuine interpretive guidance rather than a restatement, though it largely overlaps the schema's own note_scope text.

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 opening sentence gives a specific verb and resource ('获取小红书蒲公英创作者商业概览') and enumerates the returned content blocks: note scale/medians, service performance, platform tags, growth, estimated cost and comparison values. It explicitly states what it does not return ('不返回逐篇明细'), and names the sibling tools that cover those other 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?

Routes the agent explicitly: per-note performance → 创作者笔记表现工具, profile/quote → 创作者档案工具, fan composition → 粉丝画像工具, and this tool for the commercial summary plus cost reference. The daily vs cooperation selection rule is spelled out with concrete triggers ('商单、品牌合作笔记或外溢进店' vs '日常内容表现'), so the enum choice is not left to inference.

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