navtex

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

The description notes that send_message is 'callsign-gated', a useful behavioral trait. However, without annotations, it fails to disclose other important behaviors such as blocking behavior of get_message, potential side effects, or required permissions.

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 short but poorly structured: uses line breaks and inconsistent formatting (e.g., 'NAVTEX / SitorB mode' followed by a period, then a list). It could be more concise and better organized.

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 and no annotations, yet the description fails to cover essential details like return values, error handling, or prerequisites. For a tool with two operations and two parameters, this is severely incomplete.

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?

With 0% schema coverage, the description compensates partially: it explains that for get_message 'value' is timeout seconds, and for send_message 'value' is text. However, it does not describe the 'operation' parameter's possible values or format beyond listing them in the text.

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 mentions NAVTEX/SitorB mode and lists two operations (get_message, send_message), giving a general sense of purpose. However, it lacks a clear verb+resource statement (e.g., 'Manage NAVTEX messages') and does not differentiate well from siblings like 'fldigi_call', 'modem', or 'text'.

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 on when to use this tool vs alternatives (e.g., when to choose get_message vs send_message, or when to use another sibling). There are no explicit usage conditions or exclusions.

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