nvr_get_network_info

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

With no annotations provided, the description carries the full disclosure burden, and it does state 'read-only', which correctly signals a non-mutating operation. It says nothing further, but for a zero-argument informational read the remaining behavioral surface is small, and the presence of an output schema covers return values.

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 short phrase with no filler, and the resource is front-loaded. It is efficient, though almost too terse to be maximally useful.

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 simple zero-param read tool with an output schema, little is required, but the description gives no indication of what network attributes are covered or how it relates to the many sibling info tools. An agent can call it correctly but cannot confidently choose it over nvr_get_system_info or nvr_get_device_info.

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 no parameters (empty object schema), so there is nothing for the description to disambiguate. Baseline of 4 applies for a zero-parameter tool.

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 a specific resource (NVR network configuration), which distinguishes it from siblings like nvr_get_system_info and nvr_get_device_info. The verb is only implied by the tool name rather than stated, so it falls short of a fully explicit verb+resource statement.

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?

There is no guidance on when to call this versus nvr_get_system_info, nvr_get_device_info, or nvr_get_storage, all of which are adjacent read-only configuration/info tools. The parenthetical '(read-only)' hints at safe usage but does not route the agent among alternatives.

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