nvr_login

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that this performs exactly one attempt and is never retried, that automatic logins stop after failures, and that the server refuses further attempts once its failure budget is spent. These are critical operational traits beyond the empty schema.

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 definition is short and front-loaded: the primary action is stated first, followed immediately by the important caveats. Every sentence contributes operational guidance without redundancy.

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 no-parameter login tool with an output schema already present, the description is complete enough: it explains normal automatic behavior, when explicit login is needed, retry limits, and failure-budget consequences. No critical invocation context appears to be 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?

There are zero parameters, so the rubric baseline is 4. The description appropriately adds no parameter semantics because none exist; the schema's emptiness is not a 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 states a specific verb and resource: 'Explicitly log in to the NVR.' It also distinguishes this manual login operation from ordinary NVR tool calls by explaining that the first NVR tool call normally logs in automatically.

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 explicit when-to-use and when-not-to-use guidance: 'Normally unnecessary' because the first NVR tool call handles login, but use it after failed logins stop automatic authentication and the cause has been fixed. It also describes the failure-budget limit and refusal-until-restart behavior.

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