keyso_delete_ai_tracker_id_prompts_group

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only repeats the HTTP method and path. It fails to mention side effects, permission requirements, irreversibility, response behavior, or whether the group itself is deleted.

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 short and front-loaded with the purpose, followed by method, path, and an example URL. It contains no filler, though its brevity leaves important details unstated.

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?

For a destructive DELETE operation with an unstructured body and no output schema, the description omits critical information: how to construct the body, how groups are identified, and what response is expected. An agent would likely fail to call it correctly without additional documentation.

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%, so the baseline is 3. However, the 'body' parameter is described only as 'JSON body' with no structure or meaning, and the description adds no clarification about what group or prompt identifiers the body should contain.

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 a specific verb ('удаление' / delete), a resource (prompts within groups of an AI tracker), and provides the endpoint path. It doesn't explicitly contrast with sibling tools like keyso_delete_ai_tracker_id_prompts, but the name and path make the targeted operation reasonably clear.

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?

There is no guidance about when to use this tool versus deleting prompts without a group, or when a group-scoped deletion is appropriate. No prerequisites, context cues, or alternative recommendations are provided.

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