remnawave_users_bulk_extend_expiration_date

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

No annotations are present, and the description only labels the tool as a 'mutation'. It fails to disclose behavioral traits like confirmation requirements, side effects, or error scenarios. The schema includes confirmToken and mutationApproved fields, but the description ignores them.

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 description is a single sentence that merely repeats the tool name. It is not concise in a helpful way; it is under-specified and lacks structure.

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?

Given the tool's complexity (4 parameters, nested objects, no output schema), the description provides no information about return values, prerequisites, or behavior. It is completely insufficient for an agent to use the tool correctly.

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%, meaning none of the 4 parameters are documented in the schema. The description does not explain any parameter (payload, confirmToken, responseMode, mutationApproved), leaving the agent without guidance.

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 simply restates the tool name ('Remnawave users.bulk_extend_expiration_date (mutation)') without explaining what the tool does. It is a tautology, providing no additional clarity.

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 provided on when to use this tool versus alternatives such as remnawave_users_bulk_all_extend_expiration_date or other bulk operations. Missing context for selection.

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