wefax

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only reveals that 'send_file transmits and is callsign-gated,' but omits effects, permissions, or side effects for other operations. This is insufficient for safe invocation.

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 very concise with a front-loaded header. The list structure is functional but could be more readable (e.g., with line breaks). Every sentence adds value, though some operations lack context.

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?

Given the tool's complexity (10+ operations, 2 params, no output schema), the description is incomplete. It omits operation details, return values, prerequisites, and error conditions, making it insufficient for reliable agent usage.

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 0%, so the description must compensate. It partially clarifies the 'value' parameter for set_adif_log, set_max_lines, get_received_file, and send_file. However, it does not describe the 'operation' parameter values beyond listing names, leaving meaning ambiguous.

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 states 'WEFAX (weather fax) mode' and lists operations, clearly indicating the tool's domain. However, it does not explicitly differentiate from sibling modes like navtex, which could cause confusion for agents.

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 is provided on when to use this tool versus alternatives. The description lacks context on prerequisites, exclusions, or typical scenarios, leaving the agent to infer usage from the operation list.

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