security_descriptor_decode

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

With no annotations provided, the description must carry behavioral context, and it does: it is a bounded decode, reports structural diagnostics, and explicitly states it does not infer effective access. It does not describe potential side effects, permissions, or failure modes, but for a purely analytical decode tool this is reasonably transparent.

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 two sentences, front-loaded with the core action, and each clause adds distinct value: decode operation, input formats, reported outputs, and scope limitation. No filler or redundancy.

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 a full output schema and 100% parameter schema coverage, the description need not detail return values or parameter constraints. It covers the tool's scope and limits well, though it could more explicitly route the agent when raw bytes are not available.

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%, so the schema already documents all four parameters thoroughly, including limits and defaults. The description adds only the broad input-format constraint ('explicit hex or base64'), which is already in the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: 'Decode bounded self-relative Windows security-descriptor bytes from explicit hex or base64.' It also names the exact output content (owner/group, ACL states, ACE masks/SIDs, structural diagnostics), so an agent can tell what this tool does without opening the 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?

The description tells the agent the required input formats ('explicit hex or base64') and scope ('does not infer effective access'), which implies usage. However, it does not name an alternative tool or state when to prefer this over related tools such as evtx_describe_security_descriptor, leaving the usage decision partly to inference.

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