Pipeline Workshop Instruct

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

The description says the instruction 'modifies the current plan,' consistent with readOnlyHint=false. The examples illustrate the range of modifications but do not disclose additional behavioral traits such as whether the session state is saved, if there are any side effects like caching, or what happens on invalid input. Annotations already provide the core mutation and non-destructive hints.

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 well-structured with a clear introductory sentence followed by a bullet-point list of example instructions. It is informative but slightly lengthy; it could be more concise by trimming redundant examples. However, the structure aids readability.

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 tool complexity (natural language processing), the description covers the core functionality well. The existence of an output schema means return value documentation is not required. However, it does not mention error handling or prerequisites (e.g., session must be open and active), which might be considered minor 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?

The input schema has 100% description coverage, with clear descriptions for both sessionID and instruction. The tool description adds value by providing many examples of valid instruction content, but these are illustrative rather than specifying constraints beyond the schema. Therefore, the parameter semantics are adequately covered.

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 modifies an open pipeline workshop session via natural language. It lists numerous example instructions (add nodes, join sources, add filters, etc.), making the purpose explicit and distinguishable from sibling tools like pipeline_workshop_open (which opens a session) and pipeline_workshop_close (which closes one).

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 specifies that the instruction is sent to an open session, implying it should be used after pipeline_workshop_open. It provides a rich set of examples covering many possible modifications. However, it does not explicitly state when not to use this tool or mention alternatives for specific operations (e.g., using apply_join_condition instead of a join instruction).

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