rba_probe_runtime

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

With no annotations, the description must bear the full burden of behavioral disclosure, but it only says 'Run'. It does not mention whether this is a read-only operation, what output is produced, potential execution time, or side effects. The timeoutMs parameter hints at blocking behavior but is not explained.

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 immediately conveys the core action and resource, with no superfluous words. The exclusions list at the end naturally leads to the necessary examples.

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 tool with three parameters, no output schema, and no annotations, this description is far too sparse. It fails to explain what a probe returns, what 'target' selects, or why timeoutMs matters, leaving critical gaps for an agent attempting to use the tool.

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?

Since schema description coverage is 0%, the description must compensate by explaining parameters. It only lists the probe enum values and leaves 'target' and 'timeoutMs' completely unexplained, providing no additional meaning beyond the raw 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 action ('Run') and resource ('built-in realtime probe'), and enumerates the specific probe types that match the schema enum, making its function unambiguous and distinct from sibling tools like snapshots or file operations.

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 such as rba_development_snapshot or rba_context_snapshot. The description lacks any context about prerequisites, selection criteria, or when another 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.