Phone Restart

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

With no annotations, the description carries the burden and does well: it explains that the page is notified first, the stream reconnects automatically, and the page reloads on next idle screen. It also discloses the when_idle branch ('says so and does nothing'). It omits permission/auth requirements and error behavior, keeping it short of a 5.

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?

Front-loaded with the core action and no wasted preamble. The single complex sentence packs useful detail, though its length and nested clauses make it slightly harder to scan than a shorter structured statement.

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 an output schema exists, the description need not explain return values. It covers the important operational behavior (page notice, stream reconnect, idle reload, when_idle gating) for a restart tool without annotations. Missing auth/error details are minor relative to what is provided.

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?

Schema coverage is 0%, so the description must compensate. It thoroughly explains when_idle semantics, but the 'why' parameter is never described beyond its name/default, leaving half of the parameters opaque. Partial compensation warrants a 3.

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 and resource: 'Restart the phone server', and clarifies the trigger context ('after a merge: it serves the new page code'). It does not explicitly differentiate itself from siblings like phone_start, phone_stop, or stage_restart, but the phone-server scope is clear enough to identify the tool.

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?

Provides implied usage context ('after a merge') and explains the when_idle gating behavior. However, it does not explicitly say when to prefer this over phone_stop/phone_start or stage_restart, nor does it state when not to use it beyond the idle condition.

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