nvr_status

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

With no annotations, the description carries the full burden, and it does disclose a meaningful trait: it never logs in, so calling it will not open a session or change auth state. It also signals that lockout counters and safety policy are surfaced, which tells the agent this probe is safe to run even when an account is locked out. It stops short of stating rate-limit or lockout-triggering behavior.

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?

A single front-loaded sentence that leads with the category ('Healthcheck:') and then lists the reported facets; nothing is wasted. The telegraphic noun list is slightly terse but still readable.

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 the description need not explain return values, and it correctly focuses on what is inspected and the no-login guarantee. The remaining gap is the absence of routing guidance versus the many sibling status/info tools, which is a minor omission for a zero-argument probe.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema confirms an empty object, and the description adds no misleading argument hints.

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?

Names the tool as a healthcheck and enumerates the specific resources it reports on: reachability, offered auth scheme, lockout counters, local session state, and safety policy. This is concrete enough to separate it from a generic info getter, but it never names the closest sibling (nvr_auth_status) or explains the boundary between them.

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?

The closing 'Never logs in' implicitly contrasts this with nvr_login, hinting at when a safe, side-effect-free probe is appropriate. However, there is no explicit when-to-use or when-not-to-use statement, and no mention of alternatives such as nvr_auth_status or nvr_get_system_info, so an agent must infer the routing.

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