aiworkhub_manager_loop_rename

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

No annotations are provided, so the description carries the full behavioral burden. 'MANAGER WRITE' discloses that this mutates state, but there is no mention of permissions, whether the rename is reversible, whether it affects an active loop, or any side effects on the conversation.

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?

A single front-loaded sentence with the operation class ('MANAGER WRITE') first and no wasted words. It is tight, though the brevity comes at the cost of the missing details noted elsewhere.

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 explained. However, with zero annotation coverage and 0% parameter description coverage, a bare one-line description leaves the agent without enough behavioral or parameter context to invoke a write tool confidently.

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 description coverage is 0% for both required parameters, so the description must compensate. It only implies that session_id identifies the conversation and title is the new name, which is inferable from the parameter names alone and adds no format, constraint, or length guidance.

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 (rename) and resource (one saved manager conversation), and the 'MANAGER WRITE' prefix signals a mutating operation. It is distinguishable from the many loop_* siblings, though it never names which one (e.g. loop_new vs loop_send) it differs from.

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, when-not-to-use, or alternative routing guidance. The phrase 'saved manager conversation' implies an existing session, but nothing tells the agent how this differs from loop_new, loop_restore, or loop_rotate in the same family.

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