hs4.cameras.pan

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

With no annotations, the description should compensate. It does not disclose that this is a mutating operation requiring confirmation, nor does it mention dry-run capability or potential side effects. The only behavioral hint is the tool name 'pan'.

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, efficient and to-the-point. It loses one point for the slightly jargon-heavy 'pancamera endpoint' which could be simplified.

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 mutating tool with 6 parameters and no output schema, the description is insufficient. It lacks context on required permissions, return value, expected behavior, and relation to other camera tools.

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 67%, so baseline is 3. The description adds no parameter-level details beyond the schema. It does not explain direction enum values or the role of confirm/dryRun.

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 it's a pan/tilt command for a camera via a specific endpoint. It distinguishes from sibling tools like snapshots or config. However, the term 'pancamera endpoint' is somewhat jargonish and could be clearer.

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 guidance on when to use this tool vs alternatives. Does not mention prerequisites, permissions, or when not to use (e.g., if camera is not pan/tilt capable).

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