get_journal_by_issn

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the action and resource, but does not clarify that it's a read-only operation, what happens if the journal is not found, whether both ISSN and eISSN can be supplied together, or what fields are returned. This is a notable gap.

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 redundancy. It front-loads the action ('getir') and includes the key condition ('ISSN veya e-ISSN numarasıyla'), making it both concise and well-structured.

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?

The tool is a simple identifier lookup with full schema coverage, but the description omits the return structure, required-parameter constraints, and not-found behavior. Given the lack of annotations and output schema, a more detailed description would improve completeness, though it is minimally adequate for a basic lookup.

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 schema already documents both parameters with descriptions and examples, giving 100% coverage. The description adds the relationship that either ISSN or eISSN can be used, but does not clarify whether at least one is required or how conflicts are resolved if both are provided. Baseline 3 for high schema coverage is appropriate.

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 uses the specific verb 'getir' (get), identifies the resource as journal information in TR Dizin, and states the lookup method (by ISSN or e-ISSN). This clearly distinguishes it from sibling tools like search_journals, which perform broad searches rather than exact identifier lookups.

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 usage for direct identifier-based lookup, but it does not explicitly say when to use this tool versus search_journals, nor does it mention whether at least one of the parameters is required. The 'veya' (or) hints at alternative parameters but provides no formal guidance on selection.

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