remnawave_subscription_page_configs_delete

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

With no annotations, the description carries the full burden but only says 'mutation'. It does not disclose whether deletion is irreversible, if confirmation is needed, or what side effects occur (e.g., cascading deletions). This is insufficient for safe use.

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 very short (one line) but lacks structure and substance. While concise, it sacrifices critical information, making it minimally helpful.

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 complexity (4 parameters, nested payload, no output schema), the description is severely incomplete. It fails to specify what gets deleted, how to identify the target, or what the response looks like.

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 0%, and the description fails to explain any of the 4 parameters. The payload object is left completely undefined, and confirmToken, responseMode, mutationApproved are not described, leaving the agent without essential usage context.

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 'subscription_page_configs.delete (mutation)' which clearly indicates it deletes subscription page configs. The name reinforces this purpose, making it distinct from siblings like create, update, and get.

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 (e.g., update or disable). There is no mention of prerequisites, such as requiring a confirmToken or ensuring a config exists before deletion.

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