alpaca_dome_slew

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 states the action and the connection prerequisite, which is helpful. However, it does not disclose whether the operation is blocking, what happens if the device is not connected, or how to verify the slew completion (e.g., via alpaca_dome_status). More behavioral context would improve transparency.

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 front-loads the core purpose, and the second adds the essential prerequisite. Every word earns its place, and no filler is present.

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 command with a well-covered schema, the description covers the essential context: what the tool does, the target parameter, and the required precondition. It could be more complete by mentioning return values or error behavior, but the lack of an output schema is mitigated by the tool's simplicity.

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 baseline is 3. The description does not add extra meaning beyond the schema; the only addition is the connection prerequisite, which is not parameter-specific. Thus, no additional parameter semantics are provided.

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 with a specific verb ('Slew'), resource ('ASCOM Alpaca dome'), and target ('specific azimuth'). It distinguishes from sibling tools like alpaca_dome_status and alpaca_dome_shutter, making its unique purpose unambiguous.

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 clear usage prerequisite: the device must be connected via alpaca_device_connect. This gives context for when the tool can be used. It does not explicitly state alternatives or exclusions, but the prerequisite is a strong guideline.

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