nws_status

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

With no annotations, the description carries the full disclosure burden. 'Value-free' is a genuinely useful signal (no secrets/credentials are echoed back) and 'Return' implies a side-effect-free read, but it never states this explicitly, nor whether authentication is required — notable for a tool that itself reports authentication status.

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?

One short, front-loaded sentence with no padding. Minor deduction because 'value-free' is unexplained jargon that an agent must interpret, and the sentence compresses three distinct status domains into one clause without separating them.

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 needn't be described, and there are no parameters to document. Still, for a zero-arg status tool an agent needs to know the prerequisite (does the caller need credentials to see authentication status?) and how it differs from nws_app_status; both are absent.

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?

Zero parameters, so the baseline is 4; there are no parameter semantics for the description to explain. The schema is an empty object, so nothing is left ambiguous.

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?

Specific verb ('Return') plus a concrete set of resources: NWS configuration, authentication, and mirror status. An agent knows what the tool reports. However, it never distinguishes itself from the very close sibling nws_app_status (or from nws_capabilities/nws_verify), so sibling differentiation is missing.

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?

Usage is only implied: a 'status' tool is understood as a diagnostic/health-check call. There is no explicit statement of when to call it, when not to, or whether it should precede nws_authenticate or be used instead of nws_app_status. Nothing misleading, but nothing guiding either.

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