reboot-cameras

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

No annotations provided, so description must disclose behavioral traits. Only states 'performs an action' and reconnection effect. Does not mention potential side effects like service interruption, permission requirements, or confirmation process.

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?

Description is adequately concise but includes redundant phrases like 'this is a helpful option' and all-caps 'THIS TOOL PERFORMS AN ACTION'. Front-loaded with purpose, but could be more direct.

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 destructive tool with no output schema, description lacks details on synchronous/asynchronous behavior, effect on ongoing operations, and purpose of confirmationId. Incomplete for reliable invocation.

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 coverage is 50% (only cameraUuids has description). Description adds no parameter-specific information beyond the schema. The confirmationId parameter is left completely unexplained.

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?

Description clearly states the tool reboots cameras and causes reconnection, distinctly different from sibling tools like 'camera-tool' or 'camera-uptime-tool'. Verb+resource is specific.

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?

Mentions usage when camera has connectivity issues or needs troubleshooting, providing clear context. Does not explicitly compare to alternatives or state when not to use, but guidance is helpful.

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