node_integration_delete_integration

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

Annotations are absent, so the description carries the full behavioral burden, yet it only states the HTTP method. It does not disclose that this is irreversible, what happens to any associated resources, whether auth is required, or what the response looks like. The only non-trivial behavioral detail (the confirm preview flow) lives in the schema, not the description.

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 content is minimal but not concise in the useful sense: it is a raw endpoint line, a redundant title, and a tag line, none of which front-loads purpose or constraints. It is under-specified rather than tight.

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 with no annotations and no output schema, an agent needs confirmation semantics and irreversibility cues in the description. Those are missing; the description is little more than an HTTP signature.

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?

Two parameters with 50% schema coverage: 'uuid' is documented only by its format/pattern in the schema, and 'confirm' has a substantive schema description in Russian that explains the preview behavior. The description adds no parameter meaning at all, so it fails to compensate for the half-documented surface.

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 includes the raw HTTP verb and route ('DELETE /api/node-integrations/{uuid}') plus a title 'Delete Node Integration', which does identify the action and resource. But it is essentially a restatement of the endpoint rather than a description, and it distinguishes itself from siblings only via the name, which the agent already has. It is sufficient but not a genuine clarification.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as node_integration_get_integration_by_uuid or node_integration_update_integration. Nothing tells the agent under what circumstances this destructive operation should be selected.

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