ipc_eventlog

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description goes beyond the flags by explaining WHY it is destructive ('because it starts a process on the IPC') and by disclosing the two-step implementation (wevtutil then file read-back), which is useful context the annotations cannot carry.

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?

Three tight sentences: what it does, the boundary/alternative, and the destructive rationale. Information is front-loaded with the resource and platform scope, and no sentence is filler.

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 presence of an output schema means return values needn't be described, and annotations cover the safety profile. However, four undocumented parameters (0% schema coverage) are a real gap, and the existence of a 'confirm_token' parameter suggests a confirmation handshake that the description never mentions, leaving the calling requirements 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?

Schema description coverage is 0% across four parameters, so the description must compensate and does not. 'log', 'count', 'provider' and especially 'confirm_token' are never explained; the incidental mention of 'System Service' does not document the provider default or any format for log names. An agent must guess how to populate these fields.

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 names a specific resource (the target's Windows event log) and the exact mechanism (runs wevtutil via the System Service, then reads the result file back). It also scopes the applicable platforms (Windows 7/10/11 IPCs) and explicitly excludes CE/TC-BSD targets, so the agent can separate it from the file-system siblings like ipc_read_file without inspecting schemas.

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 gives a clear negative condition ('Not available on Windows CE / TC-BSD targets') and names the alternative for that case ('use the XAE error list for ADS logger messages there'). It does not, however, state positively when this tool should be preferred over e.g. ipc_read_file for reading log files, so the selection guidance is one-sided rather than complete.

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