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

With no annotations present, the description carries the behavioral disclosure burden. It discloses important behavior: OR-logic union across filters, automatic duplicate ISSN removal, and the inclusive/exclusive semantics of operators. It does not mention output format or error behavior, but the core query-generation logic is transparent.

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 organized with a clear purpose statement, concise bullet lists, and a relevant example. Every sentence adds useful information, and the JSON example is an efficient way to communicate the expected input shape.

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 tool with no output schema and no annotations, the description covers the ranking systems, grade semantics, operator behavior, filter combination, and duplicate handling. It does not describe the output format, but that is a minor gap given the clear generate-a-query purpose.

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%, so the baseline is 3, but the description adds meaningful value by spelling out grade sets per system, the grade-ordering semantics of 'at_least', and how filters combine. The worked example also clarifies the nested filter structure beyond the raw schema.

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 opens with a specific verb and object: 'Generate a Scopus boolean query of ISSN numbers based on journal rankings.' It further clarifies scope by enumerating the three supported ranking systems, which clearly distinguishes this tool from siblings like list_grades and list_fields.

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 gives clear operating context: how to use 'at_least' vs 'exactly', how multiple filters combine, and a complete example. It does not explicitly contrast with sibling tools or state when not to use it, but the purpose is distinct enough that an agent can infer the right scenario.

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

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

With no annotations provided, the description carries the full burden. The verb 'List' implies a non-mutating read operation, which is useful, but the description does not state whether there are any side effects, authentication requirements, pagination behavior, or output conventions. This is adequate but not deeply transparent.

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 concise sentence with no filler. The key verb-object pair is front-loaded, and every word contributes meaning.

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 the low complexity—one required enum parameter, no nested objects, no output schema—the description is nearly complete: it states what the tool returns and what input is required. It could mention the return format or sibling alternatives, but those are minor gaps for such a simple tool.

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%: the single required 'system' parameter has an enum and a description ('The ranking system to list fields for'). The tool description adds no new parameter-level meaning beyond restating the scope, so the baseline of 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 is specific: it names the verb 'List' and the resource 'available fields/disciplines' scoped to 'a specific ranking system'. This clearly differentiates it from siblings like generate_scopus_query and list_grades, which target different actions or resources.

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?

No guidance is given about when to use this tool instead of list_grades or generate_scopus_query. The only contextual hint is that it is scoped to a ranking system, but there is no explicit when-to-use or exclusionary language.

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

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

Without annotations, the description carries the behavioral disclosure burden. The verb 'List' implies a read-only operation, and 'available grades' suggests the return value is a set of grade options. However, it does not explicitly state that no side effects occur, nor does it describe response format or ordering.

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, clear sentence with no filler. It front-loads the action and object, making the tool's purpose immediately recognizable.

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 simple tool with one enum-constrained parameter and no output schema, the description is reasonably complete: it identifies the input (ranking system) and the expected result (available grades). It does not elaborate on the exact format of grades, but this is a minor gap for such a targeted list operation.

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%, and the only parameter 'system' has an enum and its own description. The description mainly rephrases the parameter's role ('specific ranking system') without adding new semantic detail beyond what the schema already 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 names a specific verb ('List') and resource ('available grades') scoped by 'ranking system', which clearly conveys the tool's purpose. It distinguishes itself from sibling tools like generate_scopus_query and list_fields, though it does not explicitly contrast with list_fields.

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 implies the tool is used when someone needs grades for a ranking system, but it provides no explicit when-to-use guidance or exclusions relative to siblings. There is no mention of when list_fields or generate_scopus_query would be more appropriate.

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