alpaca_focuser_halt

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the prerequisite (connection) but does not explain what happens on halt (e.g., whether it's immediate, whether it returns a success/failure indicator, or any side effects). For a control command, 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 a single, direct sentence plus a useful note. Every word earns its place: it states the operation, the resource, and a critical prerequisite without fluff.

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, the description is adequate: the schema covers parameters and the note covers the main prerequisite. However, the absence of any information about the command's effect (e.g., whether it is a blocking call or what response to expect) leaves some gaps, especially given no output schema or annotations.

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 has 100% documentation coverage for all three parameters (ip, port, device_number). The description adds no parameter-specific information beyond the schema, so the baseline 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 action ('Halt') and the resource ('ASCOM Alpaca focuser'), which exactly matches the tool name. It distinguishes itself from sibling tools like alpaca_focuser_move and alpaca_focuser_status by specifying the halt operation.

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 an explicit prerequisite: 'Device must be connected first using alpaca_device_connect.' This provides clear context for when the tool is valid. It doesn't mention alternative tools for other focuser operations, but the name and purpose make the intended use obvious.

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