alpaca_telescope_slew

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

With no annotations provided, the description must bear the burden of behavioral disclosure. It mentions the need for prior connection and coordinate systems, but does not disclose whether slew is synchronous, what errors might occur, or any side effects. This is a moderate gap for a control 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 two sentences, front-loaded with the primary action and followed by a crucial note. Every word earns its place; no 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?

The tool has 7 parameters and no output schema or annotations. The description covers the core action and connection prerequisite but leaves ambiguity about parameter combinations (both RA/Dec and Alt/Az provided?) and expected return behavior. For a moderate-complexity control tool, this is adequate but has clear gaps.

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%, so the schema already documents all seven parameters in detail. The description adds only the concept of coordinate systems (RA/Dec or Alt/Az) but doesn't clarify how parameters interact (e.g., whether both pairs are required mutually exclusive). This is minimal added value beyond the schema.

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 'slew' and the resource 'ASCOM Alpaca telescope', with coordinate specification (RA/Dec or Alt/Az). This distinguishes it from sibling tools like status, park, tracking, and abort.

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 key prerequisite: 'Device must be connected first using alpaca_device_connect.' This gives clear context for when to use the tool, though it doesn't explicitly contrast with alternatives. The verb 'slew' inherently differentiates from other telescope actions.

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