swarm_unlock

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

Describes the unlock operation as non-destructive, notes the node's inability to serve API requests while locked, explains that the node resumes automatically, and clarifies the need for autolock to be enabled. Adds context well beyond annotations.

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?

Well-structured with clear sections: purpose, context, usage, parameter. No unnecessary sentences, front-loaded with primary action. Efficient and easy to parse.

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?

Covers all essential aspects: prerequisite (autolock), location restriction, key source, return value (bool), and behavioral notes. Output schema exists and description clearly explains it. Complete for a single-parameter tool.

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 only parameter 'key' is described as 'the swarm unlock key (from swarm_unlock_key)', adding critical sourcing context that the schema type 'string' alone does not provide. Schema coverage is 0%, so description carries full burden.

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 the verb 'unlock' and the resource 'manager node', distinguishing it from siblings like swarm_init, swarm_unlock_key, etc. It specifies the scenario (autolock enabled after restart) and relates to other swarm tools.

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?

Explicitly states when to use (locked manager after restart) and when not (no autolock), the requirement to call on the locked node directly, and alternative tool swarm_unlock_key to retrieve the key. Provides actionable guidance.

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