enable_toolset

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

Without annotations, the description must disclose behavioral traits. It only states the action 'enable' and the prerequisite, but omits details on side effects, reversibility, permissions, or what changes occur (e.g., new tools appear, session impact). This leaves significant ambiguity.

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 sentences: the first states the purpose, the second provides usage guidance. It is front-loaded and contains no unnecessary words, earning its place.

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 and prerequisite. However, it lacks details on what enabling entails (e.g., persistence, session scope, return value), making it marginally complete but not fully informative.

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 covers the parameter with a description. The tool description adds value by referencing get_toolset_tools and list_available_toolsets, guiding users on where to find valid toolset names. This cross-reference enhances the semantic meaning 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 clearly states the tool enables a toolset, using the verb 'enable' and the resource 'one of the sets of tools'. It also mentions prerequisite tools (get_toolset_tools, list_available_toolsets), which distinguishes it from related tools like disable_toolset.

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 explicitly instructs users to first use get_toolset_tools and list_available_toolsets, providing clear context for when to use this tool. However, it does not mention when not to use it or alternative tools beyond the implied disable_toolset.

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