set_active_solution

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

Describes matching behavior and return value (full path). However, no annotations exist, and the description does not disclose failure modes, prerequisite state, or side effects beyond switching the active solution.

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?

Two sentences, front-loaded with purpose, followed by matching details and return value. No extraneous 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 covers purpose, matching semantics, and return value. Missing error conditions or prerequisites, but adequate for the complexity.

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 describes the single parameter as a partial or full name. The description adds 'case-insensitive' behavior, which is meaningful beyond the schema. With 100% schema coverage, the description adds useful 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?

Clearly states the tool switches the active solution and that subsequent calls operate on that solution. Mentions partial case-insensitive matching, which distinguishes it from related tools like load_solution or list_solutions.

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?

Implicitly advises use before other solution-dependent calls. No explicit when-not-to-use or alternatives listed, but the context of sibling tools provides some guidance.

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