Recommend Target Journals

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

No annotations provided, so description carries full burden. It discloses that it's free, runs locally via FTS5 + topic-RAG with no LLM call, and lists output fields. Missing details on error handling or side effects, but these are minor for a read-only tool.

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 sentences with a clear front-loaded purpose and a concise list of output fields. Every word serves a purpose, no wasted text.

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?

Despite no output schema, the description details all output fields (grade, match %, tier, etc.). With 8 parameters including a nested filter, the description covers the tool's functionality comprehensively.

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%, with each parameter having a description. The description adds no additional meaning beyond summarizing the schema. Baseline of 3 is appropriate as it repeats but does not enrich.

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 clearly states 'Recommend ranked target journals for a paper from a ~1,200-venue index,' specifying the verb, resource, and scope. This directly differentiates it from sibling tools like check_duplicate_publication or find_research_gaps.

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?

Explicitly states usage context: 'Use when the user asks "where should I submit this paper" or wants to compare target venues before deciding.' This provides clear guidance, though it doesn't mention when not to use or alternatives, which is acceptable given distinct siblings.

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