Sb3 Vm Stub Calls

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

With no annotations, the description carries the burden of disclosing side effects. 'Recorded' implies the tool returns previously captured data rather than mutating state, and 'since load' communicates accumulation/reset behavior. '(proxied)' adds a behavioral trait, though it is cryptic and unexplained; no details are given about side effects, ordering, or whether the call triggers the proxy.

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 short and front-loaded, with no filler. The parenthetical '(proxied)' is terse but the overall structure is economical. It loses a point because the brevity creates ambiguity about the operation being described.

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?

A zero-parameter read-only diagnostic with an output schema can be minimally complete, and 'since load' gives enough context to reason about state. However, the description does not explain what a 'stub call' is, why '(proxied)' matters, or when this tool is useful relative to the many VM siblings. It is adequate but leaves clear 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?

The input schema is empty and there are zero parameters, so the description does not need to explain parameter meaning. The baseline for a parameterless tool is 4, and the description does not undermine this.

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 phrase 'Recorded pen/sound stub calls since load' identifies the resource (stub calls) and a temporal scope (since load), so an agent can guess what data is returned. However, it lacks an action verb like 'get' or 'list', and the passive noun-phrase style leaves it ambiguous whether the tool records calls or returns recorded calls. It does not explicitly distinguish itself from the many sb3_vm_* sibling tools.

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?

No guidance is provided about when to use this tool versus sb3_vm_state, sb3_vm_threads, sb3_vm_onitors, or other VM inspection tools. The phrase 'since load' hints at a lifecycle dependency, but there is no explicit instruction about when to call it or what problem it solves.

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