detach_prompt_snippet_from_flow_step

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

With no annotations, the description carries full burden. It discloses the non-destructive nature (only unlinks, snippet not deleted), the HTTP response (204 with no body), and recommends checking the stack with list_flow_step_prompts. It does not mention permissions or side effects, but these are minimal for this operation.

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 two sentences, each earning its place. The first sentence states the purpose, the second provides additional details on identification and response. No superfluous 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?

Given the single parameter and lack of output schema, the description covers the tool's purpose, behavior, prerequisite, and post-call recommendation. It is fully adequate for agent usage.

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 schema describes the linkId parameter. The description adds context by stating the source of linkId (from list_flow_step_prompts) and clarifying it's not the snippet id. This adds meaning beyond the schema's description.

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 tool removes an unlink between a prompt snippet and a flow step, with the verb 'remove' and the resource 'prompt snippet from flow step's stack'. It distinguishes from deleting the snippet itself, and the sibling list includes attach/update/reorder, making its role clear.

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 explains how to identify the link by its linkId from list_flow_step_prompts, and advises reading the stack back after the call to verify the result. It provides explicit guidance on the prerequisite and post-call action, though it does not explicitly state when not to use this tool.

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