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

With no annotations provided, the description does disclose one real behavioral trait: public/free tiers withhold source URLs, which tells the agent output may lack citations. However, it says nothing about whether this is a read-only lookup, what authentication or tier the caller holds, or how results are paginated or scoped.

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?

It is short and front-loaded, but it duplicates every sentence verbatim in Chinese and English, roughly doubling length without adding information. Every sentence would earn its place if the content were substantive; here the redundancy undercuts the brevity.

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 three-parameter tool with no output schema and no annotations, the description leaves the return shape, the meaning of 'published', and the relationship to the other intel_* tools entirely unstated. The one piece of useful context, URL redaction on free tiers, is not enough to call this 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 entity, category, and entity_id are already documented with examples in the schema. The description adds no interpretation of these parameters, which is the baseline 3 when the schema carries the explanatory load.

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 restates the tool name ('链主倒逼' / 'chain-master push') without a verb or resource indicating what the tool actually returns or does. The only added semantics are cryptic filter notes ('承接方不是定点供应商'), which don't resolve into a describable operation, so an agent cannot distinguish it from intel_chain or intel_supply siblings.

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?

There is no statement of when to use this tool, when not to, or which of the fifteen intel_* siblings covers an adjacent question. The note that the receiving party is not a designated supplier is a domain claim, not invocation guidance.

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