disable_user

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

No annotations are present, so the description must cover behavioral traits. It discloses the need for a SYSTEM token and that the reason is recorded for audit, but it omits details such as reversibility, impact on user data, or concurrent effects.

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 concise sentences front-load the purpose and add key constraints. No unnecessary words.

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 no output schema and no annotations, the description partially covers the tool's behavior but lacks details on what disabling entails (e.g., can the account be re-enabled? Are there side effects on data?). More context would improve completeness.

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 no description coverage for parameters (0%), and the description only indirectly references the 'reason' parameter by saying 'Records the given reason for audit'. The 'id' parameter is not mentioned. More explicit parameter context is needed.

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 'Disable a user account' with a specific verb and resource. It distinguishes from sibling tools like enable_user by indicating it requires SYSTEM token and records an audit reason.

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?

Provides the prerequisite ('Requires SYSTEM token') and mentions the audit side effect. However, it does not explicitly advise when to use alternatives (e.g., enable_user) or when not to use this tool.

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