Stream macOS unified logging for a bounded window

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

No annotations are provided, so the description carries the burden. It discloses the underlying command, bounded duration (≤60s), and that it returns parsed entries. However, it does not describe error handling, destructive potential, or other behavioral traits beyond the basic operation.

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 concise at three sentences, front-loaded with the core purpose. It could benefit from a more structured breakdown of parameters and usage.

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?

Given the 6 parameters and no output schema, the description is incomplete. It lacks details on return format, parameter semantics beyond duration, and how to interpret parsed entries. The absence of annotations exacerbates the gaps.

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?

The input schema has 6 parameters with only 17% description coverage (only durationSec has a description). The description adds minimal meaning beyond the schema, mainly repeating the duration constraint and default. It does not explain predicate, process, subsystem, level, or maxEntries.

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 it wraps `log stream --style compact` for a bounded duration, returns parsed entries, and is useful for capturing a specific user flow. It effectively distinguishes itself from sibling tools like logShow and other analysis tools.

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 description implies usage for capturing user flows without setting up Console.app, but lacks explicit guidance on when not to use or alternatives. It does not mention contexts where it might be inappropriate or provide exclusions.

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