pcb_close_session

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

With no annotations, the description carries the full burden. It discloses one side effect (freeing memory) but does not mention whether the operation is irreversible, whether it invalidates the session_id, or any error conditions. It also does not clarify what happens to associated data or analysis results.

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 a single, concise sentence that front-loads the primary action and side effect. Every word is informative, with no redundancy or filler.

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?

The tool is simple with one parameter, but the description lacks essential context: it does not explain the parameter, provide usage guidance, or describe the expected result/return value. The absence of an output schema increases the need for a more descriptive explanation, which is not 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?

The schema has 0% description coverage, and the tool description does not mention the session_id parameter at all. The agent is given no explanation of what a session_id is, how to obtain it, or any format constraints. The description adds no value beyond the parameter name itself.

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 action ('Close') and the resource ('a design session'), and adds the consequence 'free memory'. This distinguishes it from all sibling tools, which are analysis or query operations. The verb+resource structure is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives, such as listing sessions or other session-management tools. There is no mention of prerequisites, cleanup flows, or situations where closing a session might be inappropriate. The usage context is only implicitly derived from the tool's name and description.

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