rba_context_snapshot

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions what is captured but does not state whether the tool is read-only, whether it has side effects, requires special permissions, or how the optional screenshots are handled (especially given the two screenshot-related parameters, includeImage and includeScreenshot).

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 a single sentence that is front-loaded and efficiently lists the captured elements. It wastes no words and is highly scannable.

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?

The tool has six optional parameters and no output schema, yet the description provides no parameter details, return format, or usage caveats. It is a high-level summary but insufficient for an agent to correctly invoke the tool, especially with ambiguous screenshot parameters.

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 0%, and the description does not explain any of the six parameters (target, timeoutMs, eventLimit, focusWindow, includeImage, includeScreenshot). It only lists output categories, leaving the agent without insight into how to configure the call.

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 captures status, clients, recent events, runtime summary, and optional Roblox screenshot, which is a specific set of resources. The phrase 'in one call' hints at a consolidated snapshot, but it does not explicitly distinguish it from similar sibling tools like rba_unified_status or rba_development_snapshot.

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 on when to use this tool versus alternatives. The description implies it is for getting a broad overview, but it does not mention prerequisites, expected scenarios, or situations where a different sibling tool would be more appropriate.

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