set_ptz_position

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

Annotations indicate it is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds no behavioral context beyond the name, such as validation rules, side effects, or response details. It merely restates the action.

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 concise phrase with no wasted words. It could include more context without becoming verbose, but it is efficient and front-loaded.

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?

With 5 parameters and no output schema, the description is too brief. It does not explain what 'absolute PTZ position' entails, how to use the parameters together, or what the tool returns. The description alone is insufficient for an agent to use the tool correctly without relying heavily on the schema.

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?

All 5 parameters are already documented in the input schema with descriptions (100% coverage). The tool description adds no additional semantic information about parameters beyond the schema, so it meets the baseline for schema-rich tools.

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 'Set absolute PTZ position' uses a specific verb and resource, clearly distinguishing from sibling tools like get_ptz_position (read) and ptz_move (likely relative movement) and goto_ptz_preset (preset-based).

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 when an absolute PTZ position needs to be set, but does not explicitly state when to use this tool versus alternatives like ptz_move or goto_ptz_preset, nor does it provide when-not or prerequisite conditions.

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