Omiss Set Callsign

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

With no annotations, the description carries the behavioral load and discloses meaningful side effects: NetLogger is told which station is asking, and the callsign is shared with netlogger-mcp if installed. It does not describe overwrite behavior or error cases, but the key external sharing behavior is surfaced.

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 and front-loaded: it saves the callsign, explains the NetLogger sharing, then gives the key instruction not to guess. Every sentence earns its place.

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 single-parameter setter with an output schema, the description covers the essential context: what is saved, why it is needed once, the downstream sharing behavior, and the user-input requirement. Nothing critical is missing.

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 100% and the callsign parameter is already documented with an example. The description adds value by clarifying that it must be the user's own callsign and explicitly warning not to guess it.

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 a specific verb and resource: saving the user's amateur radio callsign. It also ties the tool to omiss_nets_on_air, so an agent can distinguish this setter from the sibling read-oriented tools.

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?

It gives clear usage context: the callsign is needed once, and the agent should ask the user for their own callsign rather than guessing. It does not name explicit alternatives or when-not-to-use conditions, but for a one-time setter that guidance is adequate.

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