free_text

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

With no annotations, the description fully discloses safety (send=false always allowed), gating (requires WSJTX_CALLSIGN for send=true), and the fact that transmitting keys the radio. Also explains edge cases for empty text. Missing details like rate limits or side effects, but sufficiently transparent for typical use.

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?

Concise overall, with two clear parts: general description and detailed behavior. The sentence about empty text is slightly dense but still understandable. No redundant information.

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 output schema and no annotations, the description covers the tool's purpose, usage scenarios, safety, and parameter behavior adequately. It explains edge cases and prerequisites. Omission of 'instance' parameter is the only 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?

Describes semantics for 'send' and 'text' in detail, explaining their interaction and defaults. However, the 'instance' parameter is not mentioned at all, leaving its purpose unclear despite 0% schema coverage.

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 'Set the free-text (Tx5) message' with a specific verb and resource, and distinguishes between safe text setting and initiating transmission (send=true). Differentiates from sibling tools like 'transmit' and 'wsjtx_call' by specifying the gated TX initiation.

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?

Explicitly describes when to use send=false (safe) vs send=true (requires WSJTX_CALLSIGN). Explains behavior for empty text in both modes. However, does not explicitly mention when not to use or alternatives to other tools.

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