vibeside_record_session

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the stateful lifecycle (start/pause/resume/stop/clear/status), which is genuinely useful, but does not state that clear destroys buffered data, whether recording survives navigation, or what status actually returns.

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?

A single front-loaded sentence with the verb first and the action set parenthesized; nothing is wasted. It is efficient, though it could have used its brevity budget on side-effect disclosure instead of pure enumeration.

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 stateful, multi-action tool with no annotations and no output schema, the description is only marginally sufficient: it names the actions but omits destructive behavior of clear, what 'status and event metrics' returns, and any permission or persistence context.

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 description coverage is 100%, so the schema already documents every parameter including the action enum and defaults. The description only restates the action list and adds no syntax or semantic detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb (Control) and resource (offline telemetry recording lifecycle) and enumerates the exact lifecycle actions, which an agent can map to the action enum. It does not, however, explicitly distinguish itself from siblings like vibeside_telemetry_get or vibeside_telemetry_clear, which also concern telemetry, so the boundary is left to inference.

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 lists the possible actions but gives no guidance on when to choose this tool versus alternatives such as vibeside_telemetry_get, vibeside_telemetry_clear, or vibeside_export_session. No prerequisites or when-not-to-use conditions are stated.

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