remnawave_snippets_delete

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

Description only labels it as a 'mutation', implying change, but does not disclose behavioral traits like destructiveness, idempotency, or the need for confirmation. The schema parameters suggest a two-step confirmation, which is unmentioned.

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 short (one sentence), but lacks structure. No separation of purpose, usage, or parameter details. It is under-specified, not concise.

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?

With 4 parameters (including a nested object), no output schema, and no parameter descriptions, the single-sentence description is grossly inadequate for an agent to correctly invoke the tool. Missing explanation of confirmation flow and payload structure.

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 with 0% description coverage. Description adds no information about parameters: payload, confirmToken, responseMode, mutationApproved. Agent gets no guidance on what payload should contain or how confirmation works.

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 states 'snippets.delete (mutation)', clearly indicating a delete operation for snippets. However, it is vague; does not specify what is deleted (e.g., snippet ID) or how deletion is identified.

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. Does not mention prerequisites, safety, or that it requires confirmation parameters (confirmToken, mutationApproved).

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