Query macOS unified logging (one-shot)

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

Describes output format (parsed entries with fields), bounds via `maxEntries`, and behavior as one-shot query. With no annotations, this is good behavioral disclosure.

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 sentences with no waste: first explains what it does and returns, second gives usage context. Perfectly front-loaded.

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 query tool with no output schema, description fully covers output fields and param constraints. Sibling tools are distinct analyses, not missing context.

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%, and the description adds no new meaning beyond the schema's parameter descriptions (e.g., 'process and subsystem sugar' is already in schema). Baseline 3.

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?

Clearly states it queries macOS unified logging via `log show`, uses specific verb 'query' and resource 'macOS unified logging', and the title flags 'one-shot' distinguishing it from streaming tools like `logStream`.

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?

Explicitly says 'Use this to look back at app logs without leaving chat', providing clear context. However, no explicit when-not-to-use or alternative sibling mention, though sibling `logStream` exists.

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