users_suspend

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state the toggle nature and mentions DirectAdmin, but it does not disclose that suspending an account is disruptive, what 'confirm' controls, whether the operation requires special permissions, or what side effects occur. The behavior is roughly stated but materially under-described for a state-changing account operation.

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 main sentence is concise and front-loaded. However, the 'Args' block duplicates and misstates schema information, and 'confirm: Required' is inaccurate. The compactness is good, but one of its few sentences actively misleads the agent.

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 suspension-related tool with no annotations, the description is incomplete. It omits the semantics of confirm, the relationship to users_unsuspend, the effect of repeated calls, and permission requirements. The presence of an output schema helps with return values, but the operation's preconditions and consequences remain unclear.

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 0%, so the description must compensate, but it fails. 'username: Account' adds little meaning. Worse, 'confirm: Required' directly contradicts the input schema, which lists username as the only required property and gives confirm a default of false. The meaning of confirm is never explained, leaving the most ambiguous parameter undocumented.

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 opens with a specific verb and resource: 'Toggle suspend/unsuspend for an account.' This clarifies that the tool is not a one-way suspend operation, which is useful given the sibling tool users_unsuspend. However, it does not explicitly distinguish itself from users_unsuspend or explain when one should be used instead of the other.

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 is given about when to use this tool versus the closely related users_unsuspend sibling. The description does not mention prerequisites, target user types, admin/reseller scope, or any exclusions. The single line 'DirectAdmin toggle' implies usage but provides no actionable decision criteria.

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