wefax

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that send_file transmits and is callsign-gated, which is useful, but it does not disclose the behavior of other operations, side effects, state changes, or what happens during reception/transmission. The description is a terse list of operation names without behavioral context.

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 compact and front-loads the mode name, but the operation list is dense and lacks formatting that would aid scanning. The final sentence about send_file is useful but could be integrated with the operation list. It is not overly verbose, but it sacrifices clarity for brevity.

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 tool with 2 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return values, error conditions, or the behavior of each operation. The callsign-gating note for send_file is a good start, but many operations (e.g., skip_apt, skip_phasing, tx_abort) are left entirely unexplained, making it hard for an agent to know when and how to invoke them.

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 0%, so the description must compensate for the schema's lack of parameter documentation. The description lists operation names and some value types (bool, int, timeout, [filename, timeout_seconds]), but it does not explain the meaning of the 'value' parameter in general, nor does it document the 'operation' parameter beyond listing possible values. The value types are helpful but incomplete.

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 identifies WEFAX as a weather fax mode and enumerates its operations, which gives a clear sense of the tool's purpose. However, it does not explicitly state what the tool does in a single verb+resource form, and the operation list is presented as a flat enumeration without explaining what each operation accomplishes.

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 by listing operations, and it notes that send_file is callsign-gated, which is a usage constraint. However, it does not provide guidance on when to use this tool versus alternatives like navtex or fldigi_call, nor does it explain which operation to choose in a given context.

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