security-disable-user

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Disables' implies a destructive mutation, it doesn't specify whether this is reversible, what permissions are required, whether it affects user sessions immediately, or what happens to the user's data. For a security mutation tool, this leaves critical behavioral questions unanswered.

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 a single, direct sentence with zero wasted words. It's perfectly front-loaded and appropriately sized for a simple tool with one parameter.

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 destructive security tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what 'disables' means operationally, what the expected outcome is, or any error conditions. The agent would be left guessing about important behavioral aspects of this mutation.

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?

The schema has 0% description coverage for the single parameter 'identity', and the tool description provides no additional parameter information. However, with only one parameter and no schema descriptions, the baseline is 3 since the description doesn't add value but also doesn't need to compensate heavily for missing schema documentation.

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 the action ('Disables') and resource ('Sitecore user account'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'security-remove-user' or 'security-unlock-user' which might have overlapping security functions, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'security-remove-user' or 'security-unlock-user' from the sibling list. There's no mention of prerequisites, consequences, or appropriate contexts for disabling versus other user management actions.

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