restart_app

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

With no annotations, the description needs to disclose side effects and operational behavior on its own. 'Restart' implies a stop/start cycle and potential downtime, but the description does not mention whether the restart is graceful, whether it fails when the service is stopped, or any permission requirements.

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 a single, clear sentence with zero redundant words. The core action is front-loaded and instantly parseable.

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 lack of annotations and output schema, the description should provide usage and side-effect context, but it does not. An agent learns what the tool does but not when to use it or what consequences to expect, leaving a notable gap.

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 schema already documents both parameters (projectName and serviceName) adequately. The description adds no further meaning about parameter usage or formats, so the baseline of 3 applies.

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 phrase 'Restart an app service' uses a specific verb and a clear resource, leaving no ambiguity about the core operation. The action is naturally distinct from sibling tools such as start_app, stop_app, and deploy_app.

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 no guidance on when to use restart_app versus alternatives like start_app, stop_app, or deploy_app. It also omits prerequisites such as whether the service must already be running.

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