delete_ros2_workflow

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

With no annotations, the description carries the full burden. It does disclose two important behaviors: preview/delete duality and refusal of foreign graphs. However, for a destructive tool it does not mention irreversibility, what happens when preview is false, how ownership is determined, or any side effects.

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 compact sentence with the core action front-loaded and a key constraint in the second clause. It is economical and scannable, though its brevity comes at the cost of useful parameter and usage detail.

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 covers enough for a basic call: identify an MCP-owned ROS 2 workflow by graph_path and rely on the preview default. But with no annotations, the meaning of command_id and idempotency_key, the actual deletion behavior, and the definition of MCP-owned remain unexplained. The output schema helps with return values, not with these operational gaps.

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%, and the description barely compensates. It loosely maps to 'preview' via 'Preview or delete' and to 'graph_path' via 'workflow', but 'command_id' and 'idempotency_key' get no explanation at all. An agent must guess their meaning from names and defaults.

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 ('Preview or delete') and the resource ('one MCP-owned ROS 2 workflow'), and adds the scope constraint that foreign graphs are refused. This distinguishes it from the many action-graph and artifact deletion siblings. However, 'MCP-owned' is not defined, which leaves some 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?

The description implies usage: preview before deleting and only for MCP-owned ROS 2 workflows, with foreign graphs refused. It does not explicitly name sibling tools for discovery (e.g., list_ros2_workflows) or state when not to use it. Guidance is present but only implicit.

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