set_tool_pack

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

With no annotations, description fully discloses key behaviors: removes out-of-pack tools, requires restart for expansion, and that removed tools cannot be re-registered. Users understand side effects.

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, first states main action, second adds essential caveats. No redundant information, highly efficient.

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 main action and behavioral nuances adequately for a simple 1-param tool. Lacks mention of return value/output schema content, but output schema exists externally.

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?

Only parameter 'pack' has 0% schema coverage, but description adds meaning by giving example value 'all' and explaining that pack decides which tools are active. Could list valid pack names for completeness.

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?

Description uses specific verb 'switch' and resource 'tool pack', clearly states it removes out-of-pack tools. Distinguishes from sibling 'list_tool_packs' which only lists packs.

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 (switch active pack) and includes critical warnings: expansion requires restart, removed tools cannot be re-registered mid-session. Provides context for limitations.

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