hs4.admin.cameras.stream_profile.set

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Set' (implying mutation) but does not disclose that confirmation is required, that dry-run is available, or that maintenance windows and change tickets may be needed. These are critical for safe invocation.

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 extremely concise at 7 words, but it is undersized for a tool with 11 parameters and complex mutation controls. It lacks structure and does not earn its conciseness by covering necessary details.

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?

Given the high parameter count, lack of annotations, and no output schema, the description is insufficient. It provides no return value hints, no mutation context, and no mention of required confirmation or administrative constraints. The agent would struggle to use it correctly without external knowledge.

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 high (82%), so baseline is 3. The description adds no additional meaning to parameters like 'camId' or 'profile' beyond what the schema provides. It does not compensate for the two undocumented parameters.

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 identifies the verb ('Set') and the resource ('camera stream profile'), and the 'admin controls' qualifier distinguishes it from general camera tools. However, it does not explicitly differentiate it from siblings like hs4.admin.cameras.config.update, leaving room for ambiguity.

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 use this tool versus alternatives, no prerequisites listed, and no mention of when not to use it. The description is a single sentence with no contextual cues for selection.

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