security-export-account

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds substantial context beyond them: the side effect is a filesystem write on the CM server, the response is a file path, the operation throws a NullReferenceException on pre-8.0 SPE (with issue references), and it should be avoided on SitecoreAI. This is exactly the kind of behavioral disclosure that earns a top score.

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 compact sentences, front-loaded with purpose and output, followed by the version prerequisite and platform caveat. No filler, though the parenthetical issue references and version caveat add some density.

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?

With no output schema, the description usefully states the return value (file path), discloses the write side effect and its environment requirements, and warns about failure modes. An agent has everything needed to decide whether to call it and what to expect.

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 all four parameters (path, root, identity, accountType) are already documented, including their mutual exclusivity. The description adds no parameter-level detail such as path syntax or how identity strings interact with accountType, so the baseline 3 applies.

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 precise verb and resource ('Exports (serializes) a Sitecore user or role'), names the destination ('the CM's own filesystem'), and reveals the return value ('the file path'). An agent immediately knows this is a file-producing export operation, distinct from the read/get and import/remove security siblings.

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?

Gives a clear routing rule for SitecoreAI ('prefer Sitecore CLI serialization') and a hard prerequisite ('Requires SPE 8.0 or later'). It does not explicitly name security-import-account as the inverse tool or state when-not-to-use on CM, so guidance is strong but not exhaustive.

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