remnawave_profiles_delete

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

Only states it's a mutation; does not disclose destructive behavior, auth needs, or the confirmation mechanism implied by confirmToken and mutationApproved parameters.

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?

Extremely brief but omits essential information; under-specification rather than concise completeness.

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?

Fails to cover a complex tool with 4 params, a confirmation mechanism, and no output schema; description is wholly inadequate.

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% and description adds no meaning to the 4 parameters; payload, confirmToken, responseMode, mutationApproved are entirely unexplained.

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 restates the tool name ('Remnawave profiles.delete (mutation)') without adding any new information or distinguishing from sibling tools like remnawave_profiles_create or remnawave_profiles_update.

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 mutation versus alternatives; no mention of prerequisites or confirmation requirements.

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