get_ipc_log

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

With no annotations, the description carries full burden. It discloses the read action and the optional clearing of the buffer, which is a side effect. However, it does not mention whether the operation is idempotent, what happens if no data is captured, or any authentication or rate limiting considerations.

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 a single sentence that is front-loaded with the core purpose. Every word is necessary and there is no redundancy or irrelevant information.

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 presence of 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the relationship to monitor_ipc (prerequisite), the return structure, error scenarios, or how it compares to other logging tools among the 49 siblings.

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 minimal extra meaning beyond the schema: it reiterates the optional clear behavior, but does not elaborate on the 'tail' or 'sessionId' parameters beyond what the schema already provides.

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 'Read IPC traffic captured by monitor_ipc', specifying the verb 'Read' and the resource 'IPC traffic'. It distinguishes itself from sibling log-reading tools like get_event_log, get_network_log, and get_console_logs by targeting IPC traffic specifically.

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 that this tool is used after monitor_ipc has captured traffic, but it does not explicitly state when to use it vs. alternatives, nor does it provide exclusions or prerequisites. The optional clear behavior is mentioned, but no guidance on when to use or avoid the tool.

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