evtx_get_event

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

No annotations are provided, so the description carries the full burden. It discloses one meaningful behavioral trait – that evidence fields are never shortened – but says nothing about permissions, side effects, or how max_chars interacts with that guarantee, leaving the safety/behavior profile largely undeclared.

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 tight sentences, front-loaded with the action and the key prerequisite, then the truncation guarantee. No 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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the core identity and the event_ref provenance. The main gap is the unexplained relationship between max_chars and the 'never shortens' guarantee, plus no mention of what evtx_path must point to.

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%, so the description must compensate. It adds meaning for event_ref (source-bound, produced by evtx_search) but says nothing about evtx_path or max_chars, and the 'never shortens evidence fields' claim only obliquely gestures at max_chars behavior.

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?

States a specific verb (retrieve) and resource (full normalized event) and distinguishes itself from siblings by naming evtx_search as the producer of the required event_ref. An agent can tell this is the detail-fetch counterpart to a search tool without reading any schema.

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 explicitly ties usage to a source-bound event_ref originating from evtx_search, giving clear context for when this tool applies. There is no explicit when-not guidance or exclusion, but the prerequisite is unambiguous.

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