node_integrations_delete

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is an irreversible mutation. The description adds nothing on top of that: no cascade effects (e.g. does deleting an integration affect nodes?), no permission requirements, no confirmation semantics, no failure modes. No contradiction with annotations, but zero added value.

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?

It is extremely short and front-loaded, which is good, but the brevity reflects under-specification rather than efficiency. There is no waste because there is almost no content.

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, no-output-schema tool, the description is inadequate: no warning about permanence, no routing to the non-destructive siblings, and no parameter guidance. The annotations cover only the safety hint, leaving the rest of the agent's decision context unaddressed.

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 single parameter uuid has 0% schema description coverage and is not mentioned in the description at all. While the parameter's meaning is largely obvious from its name and format=uuid, the description does nothing to compensate for the documentation gap, such as clarifying whether this is the integration's UUID or a node's.

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 'Delete Node Integration' is essentially the tool name with spaces substituted for underscores, providing no information an agent couldn't derive from the identifier itself. It conveys a verb and resource in the bare minimal sense, but adds no scope, no target detail, and no distinction from siblings like node_integrations_get or node_integrations_update beyond the obvious verb.

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 statement of when to use this tool versus node_integrations_list/get/create/update, no prerequisites (does the integration need to be disabled first?), and no warning that deletion is permanent. Usage is only inferable from the verb 'Delete'.

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