Gibt Frequenzgrenzen, erlaubte Modes und maximale Sendeleistung für ein Amateurfunkband zurück (IARU Region 1 / Österreich)
| Name | Required | Description | Default |
|---|---|---|---|
| band | Yes | Bandbezeichnung wie '20m', '2m', '70cm', '160m' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the return fields and the regional scope ('IARU Region 1 / Österreich'), which is useful behavioral context. The verb 'Gibt zurück' (returns) implies a read-only lookup, though it does not explicitly mention error handling or data source.
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 sentence that immediately communicates the tool's purpose and scope without any fluff. It is well-structured and front-loaded, with every word earning its place.
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 one-parameter tool with no output schema, the description is sufficiently complete: it names the three key return elements (frequency limits, modes, max power) and specifies the regional standard. It could be more explicit about the data structure, but it is adequate for an agent to correctly invoke the 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 coverage is 100%: the only parameter 'band' is fully described with examples ('20m', '2m', '70cm', '160m') in the schema. The description does not add additional parameter semantics beyond what the schema already provides, so the baseline 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 clearly states that the tool returns frequency limits, allowed modes, and maximum transmit power for an amateur radio band, with explicit scope to IARU Region 1 / Austria. This distinguishes it from sibling tools like list_all_bands (which lists bands) and check_frequency (which checks frequencies).
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 retrieving band plan details but does not explicitly state when to prefer it over alternatives or provide exclusions. The context of amateur radio bands is clear, but no direct comparison to sibling tools is given.
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.
