aiworkhub_manager_loop_restore

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

With no annotations present, the description carries the load and does disclose real traits: it is synchronous, provider-free (no model call, no cost/latency surprise), and non-creating. It stops short of saying what happens when no prior conversation exists (empty result vs. error) or whether restore mutates any stored state, which is the one behavioral gap given the 'MANAGER WRITE' prefix.

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 key distinction in sentence one, and every remaining sentence adds information (synchronous, provider-free, call site, empty-session behavior). Minor deduction for the stray markdown fence and line breaks around 'send', which fragment otherwise tight prose.

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 shape needn't be explained, and with zero params the surface is small. The description covers sync/provider-free/no-create, leaving only the empty-state response behavior unstated — a modest gap, not a blocking one.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The absence of any dims/limit/model selector is consistent with the 'last conversation' wording.

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?

Specific verb+resource ('load the last manager conversation') plus an explicit negative scope ('Does not create one') that cleanly separates it from loop_new / loop_ensure / loop_start, which are the obvious confusable siblings. An agent can pick the right tool without opening any schema.

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?

It gives situational context ('The panel calls this on open') and a boundary case ('the first send on a selected model opens the first session when none exists'), which implies when it applies. But it never names an alternative to use instead (loop_new, loop_ensure, loop_start), so the routing is only implied rather than stated.

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