alpaca_camera_status

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

With no annotations provided, the description carries the full burden. It discloses a critical behavioral prerequisite (device must be connected) and implies a read-only operation via 'Get the status.' It also lists example fields, giving insight into what is returned. It does not detail error behavior or permissions, but for a status tool the connection note is significant.

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 long, with the primary purpose stated first and the prerequisite note second. Every sentence adds value, and there is no 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 straightforward status tool with no output schema, the description is complete: it names the device type, gives example status fields, and notes the necessary connection prerequisite. It does not describe the response format, but that is not essential given the tool's simplicity and the schema's completeness.

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 already has 100% coverage with descriptions for all parameters (ip, port, device_number). The description adds no additional parameter information, but since the schema is comprehensive, a 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: 'Get the status of an ASCOM Alpaca camera including temperature, cooler state, and exposure status.' The verb 'Get' and resource 'ASCOM Alpaca camera' are specific, and listing example fields distinguishes it from sibling status tools for other devices.

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 clear context for when to use the tool (checking camera status) and includes a key prerequisite: 'Device must be connected first using alpaca_device_connect.' It does not explicitly mention alternatives or exclusions, but the specific device focus implies separation from other alpaca status tools.

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