list_journals

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

No annotations are provided, so the description must fully convey behavioral traits. It does not disclose pagination behavior (e.g., cursor-based vs offset), rate limits, or what happens with empty queries. The presence of an output schema partially mitigates but the description itself is silent.

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 concise (one line plus examples) and front-loaded with the core purpose. However, it could be restructured to include parameter explanations without increasing length significantly.

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?

Given 4 parameters with no descriptions and an output schema, the description is insufficient. It omits details on pagination (cursor vs offset), query syntax, and default behavior. The examples are helpful but do not provide complete guidance for an agent to use the tool correctly without additional context.

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 has 0% description coverage, and the description does not explain each parameter beyond the examples. The examples show usage but do not define semantics for cursor, offset, or query format. The description adds minimal meaning beyond what schema provides.

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 that the tool lists or searches Crossref journals by free-text query, distinguishing it from sibling tools like get_journal (specific journal) and search_works (works search). Examples further reinforce the 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?

The description provides no guidance on when to use this tool vs alternatives, such as get_journal or search_works. It also does not explain when to use cursor vs offset for pagination. Examples show usage but lack explicit usage context.

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