set_auto_rotate

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

Describes both modes: enabled (auto-switch, agent note), disabled (errors returned). No annotations exist, so description carries full burden; it is mostly transparent but does not mention any side effects or auth requirements.

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?

Six sentences well-structured with bullet points. Front-loaded purpose, but could be slightly more concise; still 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?

Low parameter count, complete schema coverage, and output schema present. The description covers behavioral detail and use cases comprehensively without leaving gaps.

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 one boolean parameter 'enabled' with 100% schema coverage. The description restates the schema description including 'default' info, adding no new meaning beyond what the schema already provides.

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 starts with a clear verb-resource pair: 'Enable or disable automatic account rotation on rate limits.' It specifies the tool's scope (rotation on rate limits) and distinguishes it from sibling tools like set_active_account.

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?

Provides explicit guidance: enabled is default behavior; disable when managing a specific account and wanting errors instead of silent rotation. Includes 'Use this when...' statement for the disabling case.

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