nvr_list_modules

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

No annotations are provided, so the description carries the full burden and does state 'read-only' and 'no device I/O', which is exactly the safety characteristic an agent needs. It stops short of describing whether results are cached, how counts are computed, or expected cardinality, but the core behavioral profile is disclosed.

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 with no waste. Verb, resource, payload shape, and safety note all appear before any padding.

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 not required. For a zero-param read-only listing tool the description is essentially complete; only marginal guidance about using nvr_get_module_spec for deeper inspection is 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?

With zero parameters the baseline is 4; there is nothing to mis-specify and no compensating detail needed. The description correctly implies a no-argument call.

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 (List) and resource (API modules the NVR exposes), and clarifies the scope is the module inventory with call counts. Sibling tools like nvr_get_module_spec operate on a single module, so an agent can distinguish this inventory tool from the spec tool.

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 parenthetical suffix 'read-only; no device I/O' signals when this is appropriate (safe discovery). However, it does not explicitly name alternatives such as nvr_get_module_spec or nvr_describe_call for drilling into a single module/call, leaving some routing to inference.

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