keyso_post_tools_delete_double

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

With no annotations, the description carries the full burden of explaining consequences, but it only says 'cleaning implicit duplicates' and gives Method/Path. It does not say whether the operation is destructive, idempotent, synchronous, or what payload the endpoint expects beyond an empty JSON body.

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 only three lines and front-loads the semantically meaningful phrase before Method/Path. It is undeniably concise, but it is under-specified rather than efficiently complete, so it earns a middle score.

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?

There is no output schema and no annotations, so the description should explain the request body, return behavior, and side effects; it does none of that. An agent has enough to guess the endpoint but not enough to construct a correct JSON body or interpret the response.

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 100% (body, token, base_url each have a description), so the baseline is 3. The tool description itself adds no parameter detail, and the required body is an arbitrary additionalProperties object with no properties, leaving the actual payload semantics undocumented.

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 phrase 'Чистка неявных дублей' states an explicit operation (cleaning/removing implicit duplicates) and the endpoint /tools/delete_double reinforces the resource being acted on. It is more specific than a bare tool name, though it does not name the target entity type (e.g., keywords, sites) or contrast with sibling dedup tools like keyso_post_tools_unique.

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 given for when to choose this tool over the many nearby alternatives such as keyso_post_tools_unique, keyso_post_tools_combine, or keyso_post_tools_suggest. The Method/Path lines state HTTP details but do not explain context, prerequisites, or conditions.

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