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

It discloses behavior well beyond the annotations: login is required, the result is publicly visible, the operation invokes a real LLM that is expensive and slow, identical text is deduplicated (explaining the idempotentHint), and it enumerates specific failure codes with recovery policy. Annotations already cover write/safety profile, and the description substantially enriches it.

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 login requirement and purpose are front-loaded, but the body is a dense run-on of semicolon-joined clauses mixing jargon, error codes and a combo-chain note. Most content earns its place, yet the cryptic 'declaredContext/source inferred' fragment and packed error list reduce readability.

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?

With no output schema and a mutation tool, the description covers the essentials: login prerequisite, public visibility, dedup behavior, the follow-up read tool, and error recovery. It stops short of describing the response shape, but for a write tool with annotations declaring safety, this is largely 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 coverage is 100%, so the schema already documents all three parameters, giving a baseline of 3. The description adds real meaning by specifying what 'describe' should contain (whom you serve, what you provide, how you deliver), the 5-500 char limit and public visibility, and clarifies the user-vs-product subject selection.

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 concrete verb+resource: after confirmation it positions ('归位') the user or one of their own products (from get_my_products) in the industry chain via a free-text description. It names related tools (get_my_products, get_chain_anchor) so an agent can place it among siblings, though the dense jargon ('declaredContext', 'source inferred') slightly muddies the core purpose.

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?

It gives explicit follow-up routing ('set→get_chain_anchor'), plus concrete error handling: on position_unclear ask who/what, on relations_unclear ask upstream/downstream and do not blindly retry, on chain_source_changed re-read once then retry, on llm_unavailable retry later. This is clear context and exclusions, though it doesn't contrast against alternative positioning tools like set_persona or find_positioning_task_people.

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