set_mode

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what each mode does and the stopping conditions for auto mode. This is good transparency, though it doesn't mention any side effects of switching modes or what happens if the mode is already set.

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 concise sentences, each dedicated to one mode. There is no redundancy or filler, making it easy to parse and understand.

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 annotations or output schema, the description sufficiently covers the core behavior. It doesn't address edge cases like switching to the current mode or what constitutes a 'sensitive action', but these are likely context-specific and not critical for basic invocation.

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 input schema has no descriptions for the 'mode' parameter, but the description defines both enum values ('normal' and 'auto') with specific behaviors. This adds significant meaning beyond the schema, which has 0% coverage, and helps the agent choose the correct parameter value.

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 explains what each mode does, but it doesn't explicitly state 'sets the mode to...'. The name 'set_mode' makes the purpose obvious, and the description elaborates on the behavior of each mode, distinguishing it from sibling tools by describing the interaction behavior.

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 implies when to use each mode by contrasting their behaviors (normal asks before sensitive actions, auto runs end-to-end with specific stops). However, it doesn't explicitly state 'use normal for...' or 'use auto for...', nor does it compare against alternatives. The usage context is implied rather than directly guided.

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