Restart Adapter

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

The description discloses important behavioral traits beyond annotations: it waits for the adapter to reach RUNNING state and raises InvalidStateError for non-running states. Annotations already mark destructiveHint=true and readOnlyHint=false, and the description adds state-specific behavior that is not present in the annotations or schema.

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 concise and front-loaded, with the main purpose in the first sentence followed by clear state-based behavior bullets. Every sentence conveys essential information without redundancy.

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 is simple, and the description covers the essential behavior (restart and state handling). The presence of an output schema means return values are documented elsewhere, so the description is complete for invocation purposes.

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 schema already describes both parameters (name and timeout) with 100% coverage. The description does not add extra meaning beyond what the schema provides, so the 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 restarts an adapter on Itential Platform, with a specific verb and resource. It distinguishes from siblings like start_adapter and stop_adapter by focusing on restarting an already-running adapter, and it clearly explains state-dependent behavior.

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 by explaining that restart only works when the adapter is RUNNING and fails for STOPPED/DEAD/DELETED states. While it does not explicitly mention alternative tools like start_adapter for stopped adapters, the state-based guidance makes the intended usage clear.

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