wsjtx_call

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

Discloses that keying messages are refused unless WSJT_CALLSIGN is set. Lists allowed message types. No annotations provided, so description carries full burden; mentions mutation (build and send) but lacks details on error behaviors.

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?

Three efficient sentences plus an example; each sentence adds value, front-loaded with purpose. No wasted words.

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 no annotations or output schema, the description provides reasonable guidance but lacks details on return values, errors, and the 'instance' parameter. Adequate but not complete for a 3-param 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?

Explains 'message' and 'fields' parameters with examples and allowed values. However, 'instance' parameter is not described. Schema coverage is 0%, so description compensates partially but not fully.

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?

Clearly states 'Escape hatch: build and send any WSJT-X message type by name.' Lists allowed message types, distinguishing it from sibling specific tools like clear, configure, etc.

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?

Labels itself as 'escape hatch' implying use when no specific tool exists. Provides examples and notes a transmit gate condition, but doesn't explicitly state when not to use or alternatives.

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