evtx_describe_security_descriptor

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

With no annotations, the description must carry full behavioral burden. It adds useful context: preserving provenance and not inventing missing SIDs, reporting placeholders like 'Malformed Security Descriptor.' However, it does not clarify whether this is a read-only operation, what permissions are required, or what the output looks like beyond what the output schema provides.

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 tightly written sentences with no wasted words. The core purpose is front-loaded, and the second sentence efficiently adds a key behavioral guarantee about provenance and missing SIDs.

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 tool with six parameters, three required, and only 50% schema description coverage, the description is too sparse. It does not compensate for undocumented parameters, lacks usage guidance, and provides minimal behavioral context. The presence of an output schema covers return values, but overall completeness is low.

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 only 50% (encoding, max_aces, and max_chars have descriptions; field, event_ref, and evtx_path do not). The description does not mention any parameters or add meaning beyond the schema, leaving three parameters undocumented in both schema and description.

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 a specific verb and resource: 'Describe a security-descriptor value in a source-bound EVTX event.' It distinguishes itself from generic EVTX tools by scoping to security descriptors and emphasizing provenance. However, it does not explicitly differentiate from the sibling tool 'security_descriptor_decode', so it falls short of a 5.

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?

No guidance on when to use this tool versus alternatives like 'security_descriptor_decode' or other EVTX tools. The description implies it is for describing security descriptors in EVTX events, but there are no explicit conditions, exclusions, or prerequisites.

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