restart_application

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 explicitly mentions that the tool waits for the RUNNING state and raises InvalidStateError for certain states, which are important behavioral traits. It does not detail the internal mechanics of restart, but the key failure and waiting behaviors are disclosed.

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 appropriately sized and front-loaded. The purpose is stated in one sentence, followed by a concise bullet list for state-dependent behavior. Every sentence earns its place with no fluff or repetition.

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?

Given the tool's simplicity (2 params, no nested objects, output schema present), the description is largely complete. It covers the core behavior and error states. It might benefit from noting prerequisites like permissions, but that is not essential for a restart tool with schema and output schema coverage.

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%, with both 'name' and 'timeout' already described in the schema. The description adds no additional parameter semantics 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 verb and resource: 'Restart an application on Itential Platform.' It distinguishes this from sibling tools like start_application and stop_application by focusing specifically on restart behavior and state-dependent outcomes.

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 state-based context: it works when the application is RUNNING and fails with InvalidStateError for STOPPED/DEAD/DELETED. This implies when to use the tool (and when not to), though it doesn't explicitly name alternative sibling tools like start_application for non-running states.

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