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

With no annotations, the description carries the burden and explicitly discloses the irreversible destruction of the group and its check history, plus the requirement to pass confirm: true. It does not address errors or permission requirements, but the core destructive behavior is transparent.

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?

Two short sentences, each earning its place: the first states the function and scope, the second gives the essential safety instruction. No redundancy.

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?

The description is largely complete for a destructive tool: it states what is deleted, warns about irreversibility, and instructs the confirmation flow. An output schema exists, so return values need not be described. The only notable gap is the unmentioned 'section' parameter.

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%, so the description must compensate. It clarifies that 'group' is the deletion target and that 'confirm: true' is required to execute, but it says nothing about the optional 'section' parameter, leaving its role 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?

The description starts with a specific verb and resource: 'Удаляет группу вместе с историей проверок' (deletes a group along with its check history). This clearly distinguishes the tool from siblings like parsee_remove_from_group (removal from a group) and parsee_rename_group.

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?

It provides a clear usage protocol: because deletion is irreversible, the agent must first ask the user and then call with confirm: true. It does not explicitly contrast this tool with alternatives or state when not to use it, but the context is unambiguous.

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