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

Annotations already mark this as a non-read, idempotent, non-destructive write, and the description adds significant behavioral context: it is a full slow/expensive LLM re-derivation, identical submits are deduplicated (deduped=true), the declared position is pinned and will not be overwritten by later automatic pushes, and it is an externally visible write affecting how others see the user in the chain. No contradiction with annotations.

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 well-structured with bolded section headers and front-loaded purpose. Every part carries operational information, though some sentences (e.g., the comparison to the app's manual flow) are explanatory rather than directly actionable. It is appropriately sized for the tool's complexity, but slightly less crisp than a minimal high-quality definition.

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 covers prerequisites, combination flows, dedup behavior, external visibility, and all named failure branches with response keys and follow-up actions. However, since there is no output schema, the success response shape is left vague—only deduped=true is mentioned. This is a minor gap given the post-success verification path is described, but it prevents a perfect score.

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%, so the baseline is 3. The description adds genuine value by teaching how to compose describe ('what you do for whom, with what, delivering what', 5–500 chars, no fabrication) and by adding the rule that product positioning requires one's own product id from get_my_products. This goes beyond the schema, but not drastically enough to warrant a 5.

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 explicitly states this is 'the only free-text-to-write interface' on the platform, takes the user's words, submits them as a describe string, and has an LLM derive the chain position and merge the user into the chain network. It clearly identifies the resource (the user's or own product's chain position) and is fully distinguishable from any sibling tool.

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?

An explicit '何时用' (when to use) section opens the description, positioning it as the agent's entry point. It provides a concrete follow-up chain (get_chain_anchor → get_creator → start_conversation), rules for defaulting to 'me' vs. targeting a product, and the prerequisite get_my_products. Failure branches each come with exact next actions and explicit 'don't retry' guidance.

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