users_bulk_actions_bulk_revoke_users_subscription

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

No annotations are provided, so the description carries the full burden, and it delivers almost nothing: no indication that this is a destructive write, whether it needs confirmation, permissions required, or what happens to non-matching IDs. The only behavioral detail (preview without confirm:true) lives in the schema, not the description.

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?

Very short, but the front-loaded HTTP method/path and the OpenAPI 'Tags:' line are generator artifacts that do not help an agent. The one meaningful sentence is buried after the route.

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 bulk destructive mutation with no annotations and no output schema, the description is far too thin: it omits confirmation semantics, batch limits, and error/permission behavior. What exists is largely a restatement of the endpoint.

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 coverage is only 50%: the confirm parameter is documented in the schema, but userIds has no description. The description's 'by User IDs' adds marginal meaning and omits the useful constraints (1-500 items) that a caller would want to know.

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?

States a specific verb (revoke) and resource (users subscription) with a clear bulk scope ('by User IDs'), which distinguishes it from the single-user sibling users_revoke_user_subscription. The raw POST path and 'Tags:' line add noise rather than clarity, but the core purpose is unambiguous.

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 on when to use this bulk tool versus users_revoke_user_subscription, and no prerequisites or conditions are given. The 'bulk' scope is only implied by the tool name and the plural 'User IDs'.

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