Set client mode

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

With no annotations provided, the description carries the transparency burden. It discloses the behavioral differences between modes (diagnostic vs. full geometry streaming) and notes the effect on teleport_get_geometry. It doesn't mention side effects of switching modes but is sufficiently transparent for the tool's purpose.

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?

Two sentences, every word earns its place. It front-loads the mode explanations and includes actionable guidance without 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?

Given the moderate complexity (2 params, one enum) and presence of an output schema, the description adequately covers the modes and intended usage. It references connectionId implicitly via the connection context, and the output schema handles return values. Minor gap: doesn't explicitly state prerequisites like an active connection.

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 50% (connectionId is described in schema). The description adds meaning to the 'mode' parameter by explaining each enum value, while connectionId is already well-documented. This compensates for the coverage gap.

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 title 'Set client mode' clearly states the tool's purpose, and the description elaborates on the two modes. It distinguishes from siblings like teleport_set_pose by focusing on mode selection, though it doesn't explicitly mention alternatives.

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 explicit guidance for when to use the 'simulated' mode ('Use simulated before expecting teleport_get_geometry to report anything') and explains 'minimal' as a diagnostic. It gives context for mode choice but does not discuss when to use this tool vs. alternative tools.

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