Berechnet die Kabeldämpfung für verschiedene Koaxialkabeltypen bei einer bestimmten Frequenz und Länge
| Name | Required | Description | Default |
|---|---|---|---|
| cable_type | Yes | Kabeltyp | |
| frequency_mhz | Yes | Frequenz in MHz | |
| length_meters | Yes | Kabellänge in Metern |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosure. It indicates a calculation operation with no side effects, but it does not describe the output format (e.g., dB), limitations, or any assumptions about cable data. The constraints in the schema are not referenced in the description.
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, focused sentence in German that immediately states the tool's purpose. There is no verbose repetition or unnecessary detail, making it highly 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 has no output schema, so the description should explain the return value (e.g., total attenuation in dB), but it does not. It also lacks guidance on limits or validity, though the schema defines them. For a simple calculation tool, the missing output info is a notable gap.
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 covers 100% of parameters with descriptions, so the baseline is 3. The description only restates the concepts of cable type, frequency, and length without adding practical meaning, such as typical values or the meaning of the result. Thus, it adds no value beyond the 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 clearly states the tool calculates cable attenuation for various coaxial cable types at a given frequency and length, using a specific verb and resource. It distinguishes itself from sibling tools like calculate_wavelength or compare_cables by focusing on attenuation.
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 context is clear: it is for calculating cable loss based on frequency and length. However, it does not explicitly mention alternatives or exclusions, such as when to use compare_cables instead. The scenario is specific enough to guide usage without being fully explicit.
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.
