dahua_nvr_ptz

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It indicates this is a control (non-read-only) operation, but it does not mention potential side effects such as physical camera movement, failure conditions, or whether the command is asynchronous. This is minimal disclosure.

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 description is a single sentence that is front-loaded with the core purpose, lists example actions, and contains no redundant words. It is concise and 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?

For a control tool with 6 parameters and no output schema, the description is adequate but not complete. It lacks guidance on command syntax, expected results, or prerequisites. The schema covers parameter details, but the description does not explain the tool's overall behavior beyond its basic purpose.

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?

Schema description coverage is 100%, with each parameter having a description. The description mentions action types but adds no extra detail beyond the schema. Since the schema already documents all parameters, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose with a specific verb 'Control' and resource 'PTZ camera connected to a Dahua NVR', and lists example actions (pan, tilt, zoom, preset). This effectively distinguishes it from sibling read-only tools like dahua_nvr_system_info and dahua_nvr_channel_status.

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 description implies usage for controlling a PTZ camera but does not explicitly provide when-to-use or alternative guidance. It does not mention exclusions or compare to sibling tools, which would be helpful given the presence of other Dahua NVR tools.

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