set_realtime

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

With no annotations, the description carries full burden. It discloses the key behavior: enabling causes frame skipping to maintain target FPS, disabling plays every frame. This is transparent for a boolean toggle, though it could mention default state or idempotency.

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 extremely concise: two sentences plus an args list. It front-loads the purpose and adds critical behavioral detail efficiently. Every word earns its place, 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 simple boolean toggle tool, the description covers purpose, parameter semantics, and behavioral effect. Output schema exists, so return values are covered elsewhere. No missing crucial information for this complexity level.

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 0% (no parameter description), but the description fully compensates with explicit Args: 'True to enable realtime, False to play every frame.' This adds complete semantic meaning beyond the type and default in the schema.

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 tool's purpose: 'Enable or disable realtime playback mode.' It specifies the verb (enable/disable) and the resource (realtime mode), and adds behavioral context (frame skipping to maintain FPS). This distinguishes it from siblings like set_fps (sets target FPS) or play (starts playback).

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 usage for controlling playback performance but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. It only describes the effect, leaving the agent to infer context without direct guidance.

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