alpaca_rotator_halt

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It notes the connection prerequisite, which is valuable, but does not detail other behaviors such as what happens if the device is already halted, whether the command is asynchronous, or error handling. This is borderline sufficient for a simple halt 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 extremely concise: two short sentences. The first sentence delivers the purpose, and the second adds a critical prerequisite. No wasted words or redundant information.

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 simple halt command with no output schema, the description is adequate but incomplete. It explains the purpose and a prerequisite, but does not discuss return values or error conditions. Given the low complexity and full schema coverage, this is acceptable but not exceptional.

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 100% coverage for all three parameters (ip, port, device_number), each with a description. The tool description adds no additional parameter-specific meaning beyond that, so the baseline score of 3 is appropriate.

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 the tool's function: 'Halt an ASCOM Alpaca rotator.' This specifies a definite action (halt) and a clear resource (rotator), distinguishing it from sibling tools like alpaca_rotator_move and alpaca_rotator_status.

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 provides a critical usage prerequisite ('Device must be connected first using alpaca_device_connect'), giving clear context for when this tool can be invoked. It does not explicitly mention exclusions or alternatives, but the purpose statement implies the primary use case.

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