Set Session Context

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

The description adds context beyond the readOnlyHint annotation by explaining that billing and organization/access are read-only and that certain toolsets are unavailable. It also mentions that most toolsets start hidden, which is useful behavioral info.

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 slightly long but each sentence adds value: the purpose is front-loaded, the prerequisite is clear, and the additional notes about incomplete areas and hidden toolsets are relevant. No redundancy.

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 session-setup tool, the description covers the purpose, prerequisite, and important limitations. It doesn't explain return values, but that's not necessary for a set operation. It adequately prepares an agent to call it correctly.

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% for parameters, but the description adds specific guidance by stating that IDs are public GUIDs and clarifies the optional projectId. This adds value beyond the schema's generic descriptions.

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 verb 'set' and the resource (active organization/project context). It distinguishes itself from sibling tools by being a session prerequisite, not a data retrieval or modification tool.

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?

It explicitly states 'Must be called before using any module-specific tools,' giving a clear when-to-use condition. It also points to related tools (list_toolsets, enable_toolset) for enabling hidden toolsets, providing practical usage context.

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