metashunt_stream_now

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

With no annotations, the description carries the transparency burden. It discloses the adaptive decimation behavior and the return shape, but it does not mention side effects, failure modes, or performance implications.

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 two tight sentences with the purpose front-loaded. It uses no filler and communicates the key behavior and output format efficiently.

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 return format is described as decimated (t_us, cur_ma) plus a summary, which helps given there is no output schema. However, the parameter effects beyond max_points are unclear, leaving the operational context incomplete.

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?

Only max_points is explained as capping the output. threshold_pct and abs_min_threshold_ma are not connected to the decimation or triggering behavior, and schema coverage is 0%, so the description does not fully compensate.

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 action and resource: returning the most recent samples from the live ring, with decimation. It is clear enough to distinguish from historical/session-oriented sibling tools like slice_log and list_sessions.

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?

It implies use on live/current data, but it does not explicitly explain when to use this instead of alternatives such as burst, slice_log, or load_session. There is no when-not-to-use guidance.

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