remnawave_users_bulk_revoke_subscription

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

No annotations provided. Description only labels it as a mutation but does not disclose behavioral traits: what happens to users' subscriptions, reversibility, side effects, or required permissions. The agent lacks critical safety information.

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?

One line is not conciseness; it is under-specification. The description lacks structure and fails to present key information upfront. Every sentence should add value, but this text adds none beyond the name.

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 mutation with 4 params, nested objects, no output schema, and zero annotations, the description is critically incomplete. The agent cannot determine how to construct a valid request or interpret the result.

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 has 4 parameters including a generic 'payload' object with no constraints, but description provides zero detail about how to populate them. With 0% schema description coverage, the tool is unusable without external knowledge.

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?

Description merely restates the name as 'Remnawave users.bulk_revoke_subscription (mutation).' It adds no detail about what bulk revoking a subscription entails or how it differs from singular revoke. Sibling tools like remnawave_users_revoke_subscription have similar naming, but no distinction is provided.

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 tool vs alternatives like remnawave_users_bulk_delete_by_status or remnawave_users_revoke_subscription. No prerequisites, context, or exclusions are mentioned.

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