read_log_stream

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

With no annotations, the description carries the full load. It usefully discloses return semantics ('evidence metadata with acquisition intervals and conservative freshness') and an important caveat that device log times are not comparable with host dispatch times, but it omits whether reading consumes/advances the stream, permission needs, and volume/pagination behavior — significant for a 'read accumulated entries' tool.

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?

Purpose is front-loaded in the first sentence and each following sentence adds distinct information (return shape, actionRef behavior, time-comparability caveat). Dense and jargon-heavy, but no sentence is pure filler.

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 zero annotation coverage, no output schema, and 0% schema descriptions, the description addresses return semantics and one major caveat but leaves stream-consumption semantics, prerequisites, and sessionId behavior unspecified. Adequate, but gaps remain that an agent would have to discover empirically.

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%, so the description must compensate and it only partly does: it explains that actionRef links a known same-session/device action and that unavailable references 'collect independently', which adds real meaning. The top-level sessionId parameter is never explained, and its relationship to the 'active session' is left ambiguous.

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 and resource ('Read accumulated log stream entries for the active session'), which clearly separates it from mutating siblings like start_log_stream/stop_log_stream. It does not, however, distinguish itself from get_logs, which an agent could easily mistake for the same operation.

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 phrase 'for the active session' implies a stream must already exist, but the description never says to call start_log_stream first, nor when to prefer this over get_logs. The actionRef sentence hints at a correlation workflow without stating the condition that selects it.

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