hamravesh_restart_app

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

With no annotations, the description carries full burden. It discloses the disabled-by-default safety mechanism and the dry-run preview mode. It also states the expected effect (all pods restart). However, it does not detail consequences like downtime or whether the operation is asynchronous.

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 very concise, stating the operation and key behavioral notes in a single line with parentheticals. No unnecessary words.

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?

The description lacks return value information, error scenarios, and parameter descriptions. Given the complexity of a write operation with safety mechanisms and the presence of similar sibling tools, the description is 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 description provides no information about the parameters (app_id, org). With 0% schema coverage, the description fails to compensate, leaving the agent with no semantic guidance for the input fields.

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 'Restart an app (all pods restart)', providing a specific verb and resource. It distinguishes from sibling tools like redeploy by specifying that all pods restart, though it does not explicitly compare.

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 mentions that the tool is disabled by default (requires HAMRAVESH_ALLOW_WRITE=1) and has a dry-run preview mode, giving context on when it is usable. However, it does not provide guidance on when to use this tool versus alternatives like redeploy.

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