Go to a PTZ preset

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and repeatability profile is supplied. The description adds little beyond that: it does not say what happens if the preset name is unknown or if the camera is offline, which are the main failure modes for a motion command.

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 zero filler. It is efficient, though the terseness contributes to the gaps in the other dimensions rather than being a model of compact completeness.

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?

The output schema exists, so return values need no explanation, and the tool is genuinely simple with two required scalars. Still, an agent cannot reliably construct the 'camera' argument or know the error behavior when a preset is missing, which are the only real ambiguities and both remain unresolved.

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 0%, so the description must carry the parameter burden. It only clarifies one parameter ('preset' accepts a name or a token) and leaves 'camera' completely unqualified – no indication whether it takes a name, id, or index, despite it being required.

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?

Uses a concrete verb ('Move') plus resource ('pan/tilt camera to a saved preset'), which cleanly separates it from ptz_save_preset, ptz_remove_preset, and continuous ptz_move. It stops short of naming those siblings, so differentiation relies on the reader's inference.

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?

'Given by name or token' implies a preset must already exist, but there is no explicit when-to-use guidance, no pointer to ptz_list_presets for discovery, and no distinction from ptz_move for manual positioning. The agent must guess the workflow.

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