Recommend DOAJ journals for manuscript fit

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so no side-effect disclosure is needed. The description adds the meaningful caveat that output is discovery suggestions rather than acceptance predictions, which helps set expectations.

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 a single, well-structured sentence that front-loads the action and object. It contains no redundant filler and leaves detailed parameter information to the schema.

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, the description gives a general sense that results are discovery candidates, and the title clarifies they are journals. It does not specify the result structure such as journal names or metadata, but for a recommendation tool this is mostly sufficient; slightly more detail could improve completeness.

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?

The input schema covers all 6 parameters with descriptive comments, including guidance like 'Pass the full text, not keywords' and 'not an ISO code', so schema description coverage is 100%. The main description adds no extra per-parameter semantics beyond this, warranting the baseline score.

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 the tool suggests discovery candidates for a manuscript abstract or topic and explicitly disclaims acceptance prediction. It is somewhat less explicit about the resource being DOAJ journals, though the title and name make that unambiguous; it does not fully differentiate from sibling search tools.

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?

The description provides use context ('for a manuscript abstract or topic') and an explicit when-not ('not an acceptance prediction'). It does not name sibling tools or specify when to prefer structured search or diamond-OA filters, so it falls slightly short of fully explicit alternative guidance.

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