node_integrations_delete

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Delete a node integration' without indicating that the deletion is permanent, whether it cascades, what permissions are required, or what the response looks like. For a destructive operation, this is insufficient.

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 a single, front-loaded sentence with no wasted words. It is appropriately concise for a simple delete tool, though it may be slightly too terse in omitting helpful context. Still, the structure is efficient and direct.

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 simple delete tool with one parameter and no output schema, the description is minimal. It does not explain what happens on success or failure, any side effects, or whether the operation is reversible. Given the simplicity, more context about the destructive nature and consequences would be expected, but it is missing.

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?

The input schema fully documents the required 'uuid' parameter with a clear description ('Integration UUID to delete'), so schema coverage is 100%. The description does not add any parameter-specific meaning, but the baseline is 3 when the schema already handles it, and there is no gap to compensate for.

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 clearly states the action (delete) and the resource (node integration), using a specific verb and object. It naturally distinguishes from sibling tools like node_integrations_create or node_integrations_get by the verb, so an agent can identify the purpose without ambiguity.

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 on when to use this tool versus alternatives. The description only states the action without explaining context such as prerequisites, permanence, or when deletion is appropriate. It does not mention exclusions or alternatives, leaving the agent to infer usage from the name alone.

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