restart_service

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

With no annotations, the description carries the full burden, and it does disclose two useful facts: the operation mutates state and no dry-run preview exists, warning the agent the effect is immediate. It says nothing about required permissions, expected downtime, or whether the restart is reversible, which are the traits an agent most needs before calling a 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?

Two short sentences with the core action front-loaded and no padding. The parenthetical "(write)" and the closing clause are terse and purposeful, though the dry_run note is arguably better placed as a usage caveat than a standalone sentence.

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?

An output schema exists, so return values need not be described, but for a destructive mutation with no annotations and an undocumented parameter the description is thin. An agent still lacks permission requirements and impact expectations needed to invoke a restart safely.

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 single required parameter "name" has 0% schema description coverage, and the description adds nothing about its expected format or naming conventions. Its only parameter-related content is about an argument that does not exist (dry_run), which does not compensate for the undocumented input.

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 states a specific verb and resource ("Restart a service") and flags it as a write operation, which separates it from read-oriented siblings like get_service and list_services. It stops short of contrasting with the closer mutating siblings set_replicas or delete_service, so differentiation is only partial.

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 when-to-use guidance and no routing to alternatives among the mutating siblings. The remark "Has no dry_run argument on purpose" implies the caller cannot preview the action, but it never states preconditions or when a restart is preferable to scaling or deleting.

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