users_disable_user

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

No annotations are provided, so the description carries the full burden, yet it does nothing beyond restating the name and the raw HTTP route. It never says whether disabling is reversible, what happens to active connections/traffic, whether it requires elevated permissions, or how it differs from deletion. For a mutation tool this is a serious disclosure gap.

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?

It is short and not padded, but it is a raw OpenAPI dump rather than front-loaded prose: the method/path line leads, and "Tags: Users Controller" is pure noise that adds no decision value.

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 annotations, no output schema, and half the parameters undocumented, the description needed to explain the mutation's effect and the confirm/preview behavior but does neither. It is not sufficient for an agent to invoke this safely.

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 only 50%: userId has no description at all, and the confirm flag's meaning (preview vs. actual execution) lives only in the schema. The description contributes nothing beyond echoing {userId} in the path template, so it fails to compensate for the coverage gap.

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 gives a specific verb+resource ("Disable user") that an agent can act on, and the POST path confirms the target resource. It offers no differentiation from close siblings such as users_enable_user, users_delete_user, or users_revoke_user_subscription, so it stops short of a 5.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of the obvious alternatives (enable, delete, revoke subscription). The agent is left to infer the intended scenario entirely.

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