N1Mm Diagnostics

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

No annotations are provided, so the description carries the full burden. It discloses the diagnostic domains it inspects (connection, parse errors, memory), which is useful context, but never states that it is a non-mutating/read-only operation or whether it incurs load on the server. For a no-annotation tool this leaves a notable gap, though 'diagnostics' strongly implies a safe read.

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 short sentences, front-loaded with the tool's function and facets before the usage advice. Slightly redundant — 'Essential for production debugging' and 'First tool to call when something goes wrong' make the same point — so it is efficient but not maximally tight.

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-value detail is correctly omitted, and the purpose/usage coverage is adequate. The gap is the undocumented optional station_name parameter, which is the one piece of invocation information an agent needs and cannot get from either the schema or the description.

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?

The single parameter station_name has 0% schema description coverage and is never mentioned in the description. The description does not explain what the parameter scopes, nor what happens when it is omitted (the default is null), so an agent must guess whether a missing value means 'all stations' or 'current station'.

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?

States a specific verb/resource ('Server health and diagnostics') and enumerates the facets covered — connection, parse errors, memory — which clearly separates it from the data-retrieval siblings like n1mm_contacts and n1mm_bandmap. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

Gives an explicit trigger condition ('First tool to call when something goes wrong during a contest') plus a context ('essential for production debugging'), which is genuine when-to-use guidance. It does not state when NOT to use it or point to an alternative diagnostic/fallback tool, so it falls short of a 5.

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