Prüft ob ein Suffix in Österreich verfügbar ist. Zeigt in welchen Bundesländern das Rufzeichen frei oder belegt ist.
| Name | Required | Description | Default |
|---|---|---|---|
| suffix | Yes | 2-3 Buchstaben Suffix (z.B. "YML") | |
| district | No | Spezifisches Bundesland prüfen (1-9) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the primary behavior (checking availability and showing per-state status) and implies a read-only operation through the verb 'prüft'. However, it does not explicitly mention side-effect-free behavior, error handling, or data sources.
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 consists of two short, front-loaded sentences that efficiently state the main purpose and the output. Every word earns its place, with no unnecessary jargon or repetition.
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 description adequately covers the function and the output (per-state free/occupied status). For a simple 2-parameter tool with no output schema, this is sufficient, though the exact response structure is not specified.
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% for both parameters (suffix and district), so the description does not need to add parameter details. The tool description mentions federal states, which corresponds to the district parameter, but adds no meaning 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 uses the specific verb 'prüft' (checks) with the resource 'suffix in Österreich' and explicitly states the output 'zeigt in welchen Bundesländern das Rufzeichen frei oder belegt ist'. This clearly distinguishes it from sibling tools like callsign_lookup, callsign_validate, and callsign_suggest by focusing on availability across Austrian federal states.
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 use case is implied: when you need to check whether a suffix is available in Austria. However, the description does not reference any alternative tools or state when not to use this tool. No explicit exclusions or alternative suggestions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: calculations for different physical quantities, separate callsign functions for lookup, validation, suggestion, and availability, and band plan queries. No two tools appear to perform the same action, making selection unambiguous.
Most tools follow a verb_noun convention (calculate_, check_, list_), but the callsign_* group consistently places the noun first (callsign_lookup, callsign_validate). This split is readable but represents a mixed convention that slightly reduces predictability.
With 17 tools, the server is above the ideal 3-15 range and falls into the borderline 'feels heavy' category. While every tool has a distinct purpose, the number may be slightly unwieldy for quick selection.
The toolkit covers a broad range of amateur radio calculations (battery, cable, EIRP, wavelength, SWR, power) and callsign operations (lookup, validate, suggest, availability, database info). Some advanced features like propagation prediction are absent, but the core domain is well covered without critical gaps.
