N1Mm Current State

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only snapshot through wording ('Complete station snapshot', 'Returns ...') and lists the categories of state returned, but never explicitly declares it side-effect-free, nor mentions permissions, rate limits, or behavior when no station is connected.

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 opening snapshot line is well front-loaded, but the second sentence largely restates the same contents ('connection, contest, operator, radios' vs 'connection status, contest info, operator callsign, and full radio state'), which is redundant given an output schema already exists.

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?

An output schema exists, so return values need not be re-explained, and the description's restatement of them is wasted space. What is missing is any meaning for the station_name parameter and any behavioral framing (read-only, no-station case) for a tool with no annotations.

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% and the sole parameter, station_name, is never mentioned in the description. With one optional parameter and no schema documentation, the description should explain what station_name selects and what the null default means; it does none of that, so it fails to compensate for the coverage gap.

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 gives a concrete resource and scope: 'Complete station snapshot — connection, contest, operator, radios,' and enumerates the returned components. This clearly separates it from narrower siblings like n1mm_contacts, n1mm_bandmap, and n1mm_performance, though no sibling is named explicitly, keeping it short of a 5.

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?

'This is the first tool any AI session should call' is explicit when-to-use guidance that tells the agent to invoke it at session start. It stops short of naming alternatives or stating when NOT to use it, so it does not reach a 5.

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