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 only states 'restart' without explaining side effects (e.g., downtime), prerequisites (e.g., application must be running), or expected response. This is a significant transparency gap.

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 short sentence, making it very concise and front-loaded. Every word serves a purpose, and the structure is clear for a simple tool, though it omits some necessary context.

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 low complexity (one parameter, no output schema, no annotations), the description provides the core action and identifier. However, it lacks operational context such as when restarting is appropriate, what happens during the operation, or error conditions, making it minimally viable but incomplete.

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 has one parameter 'uuid' with 0% description coverage. The description adds 'by UUID', which merely restates the parameter name and provides no additional meaning about value format, source, or constraints. The agent gains no extra understanding beyond the schema property name.

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 uses a specific verb 'restart' with resource 'application' and identifies the key parameter 'UUID', clearly distinguishing it from sibling tools like startApplication or stopApplication. This makes the tool's purpose immediately obvious.

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 this tool versus alternatives like startApplication or stopApplication. It only states the action with no context about typical scenarios (e.g., applying configuration changes or recovering from a failed state), leaving the agent without decision criteria.

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