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

With no annotations, the description bears the full burden of behavioral disclosure, yet provides none. It doesn't state whether deletion is permanent, what happens to connected edges, whether it requires specific permissions, or what side effects occur. 'Delete' implies destruction but nothing beyond that.

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?

A single, economical sentence that is front-loaded with the action. There is no wasted text, but the brevity reflects under-specification rather than optimal conciseness.

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, three-parameter operation with no annotations and no output schema, the description is completely inadequate. It omits essential information about scope, side effects, permissions, and error conditions, leaving the agent without the context needed to invoke it safely and correctly.

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 has three required parameters with only 33% description coverage (only workspaceId is described, as 'The workspace ID'). The description adds no meaning for nodeId or workflowId, and doesn't explain the relationship between them or the hierarchical scoping (workspace > workflow > node). It fails to compensate for the low schema coverage.

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?

States a specific verb and resource ('Delete a node from a workflow'), which is marginally clearer than a tautology. However, it provides no differentiation from the many sibling delete_* tools (delete_connection, delete_transition, delete_audio_track, etc.), and doesn't clarify the context (workflow graph node vs. other node types). It's essentially a minimal restatement.

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 usage guidance whatsoever. The description doesn't say when to use this tool, what conditions must be met (e.g., node must exist, workflow must be editable), or what alternatives exist (e.g., delete_connection for edges).

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