alpaca_device_connect

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the two operations. It does not mention idempotency, error behavior, state transitions, or whether disconnecting is safe while device operations are in progress.

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, front-loaded sentence with no filler or redundancy. It efficiently states the core action and leaves detailed parameter explanations to the schema.

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?

While the schema covers parameters, the tool has no annotations and no output schema, and the description does not explain expected return values, side effects, or prerequisites. For a state-changing operation, this is inadequate for an agent to invoke it confidently.

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 100%, and every parameter already has a meaningful description, including the device_type enum and device_number default. The tool description adds no extra parameter semantics beyond loosely echoing the 'connect' parameter's meaning.

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 uses specific verbs 'Connect or disconnect' with the resource 'ASCOM Alpaca device', and the input schema's 'connect' boolean clarifies the two modes. This clearly distinguishes it from sibling tools, which focus on status queries or device-specific actions.

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 offers no guidance on when to use this tool versus alternatives. It does not mention that connecting is typically a prerequisite for device-specific commands like alpaca_camera_expose, nor does it describe when disconnecting is appropriate or any caveats.

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