common-restart-application

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds only the target (the application pool); it says nothing about downtime, dropped in-flight requests, required permissions, or scope of impact across the instance — the details that actually matter for a destructive restart.

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?

A single short sentence with the scope front-loaded and zero filler. It is efficient, though arguably terse to the point of under-specification rather than optimally concise.

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, instance-wide restart with no parameters and no output schema, the description omits the operational facts an agent needs — that this disrupts the running application, whether it can be safely called at any time, and what state it returns to. The annotations flag destructiveness but nothing explains the consequence.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter-level information is missing.

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?

States a specific verb ('Restarts') and a specific resource ('the Sitecore Application pool'), so the agent knows exactly what the tool affects. No sibling tool performs a restart, so there is no realistic confusion to disambiguate, but the description also doesn't explicitly differentiate itself from the common-* administrative family.

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?

There is no guidance about when this should be invoked — no preconditions (e.g., after config or cache changes), no exclusions, and no mention of alternatives. The agent must guess the operational context in which restarting the application pool is appropriate.

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