Query macOS unified logging (one-shot)

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

With no annotations, the description discloses that it wraps log show (a read operation), returns parsed entries with specific fields, and bounds output by maxEntries. It explains the sugar for process and subsystem filters.

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 sentences and a tag, front-loading the core purpose. Every sentence adds value with no waste.

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 six parameters (all documented in schema), no output schema, and 100% schema coverage, the description explains the output format (parsed entries with fields) and bounding. It is complete for a one-shot query 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?

Schema coverage is 100%, so baseline is 3. The description adds significant meaning: explains the sugar for process and subsystem over predicate, describes the level enum as minimum log level, and clarifies maxEntries as a cap on parsed entries.

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 queries macOS unified logging one-shot, wrapping log show with filters and sugar. It distinguishes from sibling tools like logStream (streaming) by using 'one-shot' in the title and describes the parsed output.

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 says 'Use this to look back at app logs without leaving chat,' implying a one-shot query scenario. It does not explicitly mention when not to use or contrast with alternatives like logStream, but the context implies it.

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