as_restart

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

Adds context beyond annotations: explains two-step process, force loses unsaved work. No contradiction with annotations (destructiveHint=true, readOnlyHint=false). Output schema exists, so return explanation is adequate.

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?

Well-structured with clear first sentence and separate Args/Returns sections. Minor verbosity in Args line, but overall efficient.

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?

Missing prerequisite that Android Studio must be running. With 0% schema coverage on the main param, description should compensate more, but it does provide necessary details for force and confirm. Output schema covers return values.

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?

Description adds value by emphasizing confirm is required, which is not obvious from schema alone. Schema descriptions exist for nested parameters, but top-level param lacks description; description compensates adequately.

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 it restarts Android Studio by closing then relaunching, distinguishing it from siblings like as_close or as_launch. The verb 'Restart' and resource 'Android Studio' are 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?

Explicitly requires confirm=true and mentions force parameter. While it doesn't explicitly list alternatives, the sibling tools make it clear. Could improve by noting when not to use (e.g., for close-only or launch-only).

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