switch_league

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

With no annotations, the description carries the full burden. It discloses that the tool changes the active league and that the league's board and draft state will resume where left off. However, it does not mention potential side effects like whether the previous league's state is saved automatically or any prerequisites such as requiring the league to exist.

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 short sentences, with the primary purpose front-loaded in the first sentence ('Make a different league active') and a valuable behavioral detail in the second. No wasted words.

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?

The tool has one parameter and an output schema, so the description need not explain return values. It covers the main action and the state-resumption effect, which is adequate for a simple switch operation. However, it lacks explicit mention of prerequisites or error conditions, but this is minor given the low 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?

The schema has 0% description coverage for the required 'name' parameter. The description implies 'name' refers to the league to activate, but it does not explicitly confirm that or provide details about format or uniqueness. This minimal compensation is insufficient given the 0% schema coverage.

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 uses the specific verb 'Make' with the resource 'a different league active,' clearly stating the tool's function of switching the active league. It distinguishes itself from siblings like list_leagues and configure_league by emphasizing the activation action and the behavioral consequence of resuming the board and draft.

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 provides clear context for when to use this tool: when the user wants to change the active league. It does not explicitly state alternatives or exclusion criteria, but the purpose is self-evident from the text and the sibling tool set.

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