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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds value by disclosing the return shape ('候选期刊与三档策略') in the absence of an output schema. It does not mention limits, latency, or how tiers are computed, so it stops short of rich behavioral detail.

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 pipe-delimited layout is scannable and front-loads the usage condition before aliases and return info. The alias list is somewhat long but serves a real routing purpose for mixed-language queries; nothing is padding.

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 read-only, 6-parameter tool with full schema coverage and no output schema, the description covers what it does, when to invoke it, and roughly what comes back. Only tier semantics and any input requirements beyond title remain unexplained.

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 all six parameters are already documented in the schema. The description only reinforces that title/abstract drive the recommendation, adding no syntax, format, or constraint detail beyond that. 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 names a specific verb and resource (recommend target journals) and scopes the input to title/abstract, which distinguishes it from literature-oriented siblings like pubmed_search or citation_verify. The leading 'Journal recommendation / 智能选刊 V3' merely restates the name, but the USE WHEN clause carries the real specificity.

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?

'USE WHEN: recommend target journals from title/abstract' gives a clear triggering context, and the tier vocabulary (reach/match/safe) tells the agent what kind of output to expect. It does not name an alternative tool or state exclusions, which keeps it below a 5.

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