users_disable

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds nothing beyond that: it does not say whether disabling is reversible, whether it terminates active connections or affects subscriptions/traffic, or what permissions are needed. For a state-changing account operation, this is a real 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?

Two words with no waste, but this is under-specification rather than conciseness - there is no front-loaded constraint, scope, or qualifier to structure. The size is inappropriate for a state-changing tool.

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 one-parameter mutation with no output schema, the description should at minimum define the parameter identity and the effect of disabling. Annotations cover only the safety hints, so nothing an agent needs in order to call this correctly is stated.

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% for the single required parameter, and the description does not compensate at all. It never clarifies which identifier 'userId' expects (numeric user id vs short UUID vs username), even though sibling tools like users_get_by_short_uuid exist and make that ambiguity consequential.

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 states a specific verb and object ('Disable user'), which is enough to separate it from users_delete or users_enable by keyword alone. However, it gives no scope, no sibling differentiation, and no explanation of what 'disable' actually changes for the user (access, subscription, traffic). Minimum viable rather than clear.

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 prerequisites, and no mention of alternatives such as users_bulk_update or users_delete despite a large sibling set of user mutation tools. The agent must infer everything about routing.

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