coronium_close_pool_session

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

With no annotations provided, the description carries the burden of warning about the destructive 'close all' behavior. It explicitly states that omitting session_key closes ALL sessions, which is a critical behavioral risk. It does not mention reversibility or side effects, but the main hazard is disclosed.

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 two concise sentences, front-loaded with the action and clearly explaining the optional parameter behavior. Every word earns its place, with no filler or redundancy.

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?

For a tool with one optional parameter and no output schema, the description is complete: it states the action, the parameter behavior, and the dangerous default. It is fully adequate for an agent to decide when and how to invoke it.

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 schema already fully describes the single parameter (session_key) with 'Session key to close; omit to close all', and the description repeats the same information. Since schema description coverage is 100%, the description adds no additional parameter semantics beyond the schema.

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 uses a specific verb ('close') and resource ('pool session'), and clearly distinguishes between closing one session (by key) or all sessions (by omission). This makes its purpose unambiguous and differentiates it from sibling tools that list or create pool sessions.

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 gives clear guidance on how to use the tool: pass session_key to close one, or omit it to close all. It implies the context of managing pool sessions but does not explicitly name alternatives or when not to use it. The conditional behavior is well explained.

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