unload_solution

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

No annotations present, but the description discloses key behaviors: frees memory, and if the unloaded solution was active, another takes over. This provides actionable understanding beyond just the operation name.

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?

Three concise sentences, front-loaded with purpose, no redundancy. Every sentence adds unique, useful information.

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 simple tool with one parameter and no output schema, the description fully covers purpose, usage context, matching behavior, and side effects. No gaps remain.

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 coverage is 100% and already describes the parameter as 'Partial or full solution name/path to match'. The description adds only the case-insensitivity detail, offering marginal additional value.

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 ('Unload a previously loaded solution') and its purpose ('to free memory'). It distinguishes itself from its complementary sibling 'load_solution' by emphasizing the memory reclamation aspect.

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 ('when you're done analyzing a codebase'), provides matching behavior details ('partial, case-insensitive name'), and implies consequences ('another loaded solution becomes active'). Missing explicit 'when not to use', but sufficient context.

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