alpaca_filterwheel_set

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the connection prerequisite but fails to explain error handling, idempotency, or side effects of moving the filter wheel. For a mutating operation, this is a significant gap.

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 two sentences, with the main purpose front-loaded. The note about connecting first adds necessary context without waste. No redundancy or filler.

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 schema fully covers parameters and the note addresses the key prerequisite. However, with no output schema and no annotations, the description does not explain return values or failure modes, leaving it minimally viable for a simple setter tool.

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?

The input schema provides complete descriptions for all four parameters (100% coverage), including 'position' being 0-indexed. The description adds no additional parameter meanings beyond what the schema already documents.

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 states a clear verb+resource: 'Set the position of an ASCOM Alpaca filter wheel.' This distinctly identifies the tool's function and differentiates it from siblings like alpaca_filterwheel_status, which reads status rather than setting position.

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 includes a valuable prerequisite ('Device must be connected first using alpaca_device_connect'), implying when to use the tool. However, it does not explicitly discuss when not to use it or compare it to alternatives, so usage guidance remains partially implied.

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