nvr_get_recording_status

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

With no annotations, the description carries the full behavioral burden, and it does contribute two useful facts: the call is read-only and the reply is raw/unparsed. However, it says nothing about permissions/auth requirements, error behavior, or whether "raw" means an unnormalized vendor payload the agent must interpret.

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 terse phrase with no filler and the key qualifier (read-only, raw reply) placed inline. It is efficient, though bordering on under-specified rather than truly well-structured.

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 need not be explained, and there are no parameters to document. The remaining gap is disambiguation — for a tool sitting among ~40 NVR siblings, the description does not tell the agent when this status call is the right one.

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 per the rubric the baseline is 4; there is no parameter semantics to clarify and the schema trivially matches the description.

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 resource area ("Recording / storage policy status") but the phrase is ambiguous — it could mean live recording activity or the stored recording policy config, and it does not distinguish itself from siblings like nvr_get_storage, nvr_status, or nvr_list_recording_segments. There is no clear verb+object that lets an agent pick this over those neighbors.

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?

No when-to-use guidance is given, and none of the many adjacent tools (nvr_get_storage, nvr_status, nvr_list_recording_segments) are named as alternatives. The agent must guess from the ambiguous name alone.

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