Real-Time Analyzer

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether start/stop are stateful mutations, whether reset discards captured data, whether capture blocks until an average completes, or what the read_* actions return. Only the verb "Control" hints at mutation.

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?

Two short sentences, front-loaded with the resource before the actions, so it is easy to scan. However, the action enumeration duplicates the schema's enum verbatim and consumes most of the text without adding information. It is not padded, but it spends its budget on redundancy rather than on the missing behavioral detail.

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?

This is a relatively complex tool: eight distinct actions, a nested config object, no annotations, and no output schema. The description should therefore explain statefulness, prerequisites, and what the read_* actions yield, and it does none of these. It is a capability list rather than a usable specification.

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 action, the enum, and the nested config fields (window, fft_size, averaging). The description adds no meaning beyond restating the enum values, and does not clarify which actions require config or what units/config values are valid. Baseline 3 applies.

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 states a specific verb ("Control") and a specific resource ("REW Real-Time Analyzer via API"), then enumerates the eight supported actions. That is enough to separate it from siblings such as rew_api_generator, rew_api_spl_meter, or rew_api_eq. It stops short of 5 because the action names are not explained, so an agent cannot tell what distinguishes capture from read_captured beyond the name.

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 when-to-use guidance is given: nothing says whether this is the right tool versus rew_api_spl_meter or rew_api_measure, nor whether a connection via rew_api_connect must exist first. The action list implies capabilities but not conditions or ordering. The reader is left to infer workflow entirely.

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