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

Annotations already mark it readOnly and openWorld, and the description adds valuable non-obvious behavior: a successful call deducts 20 credits while a failed call does not, and the returned data uses 蒲公英 commercial accounting. This goes beyond the annotations without contradicting them; no mention of rate limits or response shape is needed because the 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?

Two compact sentences: the first states the operation and its key output fields, the second conveys the crucial commercial-scope and cost semantics. No filler or repeated schema content.

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 single-required-parameter, read-only lookup with a full output schema, this is complete. It covers the commercial nature, the exact input identifier, the fields returned, and the credit cost – everything an agent needs to decide and execute 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 coverage is 100% and the note_id parameter already has a thorough description covering exact usage and prohibitions on truncation/formatting. The tool-level description adds no parameter-specific semantics beyond naming note_id in the first sentence, so the baseline 3 applies.

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 opens with the exact verb and resource: getting XHS 蒲公英 commercial enhanced note detail by note_id, and lists the returned fields (正文, 图片/视频摘要, 作者, 曝光量, 阅读量, 互动量, 报价). It also explicitly distinguishes itself from ordinary public note detail, so an agent can tell it apart from sibling xhs_get_note_detail_by_note_id and the by_url variant.

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 clearly positions this as the commercial (蒲公英) data path and warns it is not the same as ordinary public note detail, which implies using it when business-side enhanced metrics are required. It does not name alternatives explicitly or state when-not-to-use beyond the commercial/non-commercial distinction, so it falls just short of full explicit routing.

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