transform_execute

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does so unusually well: it warns that an invalid function type, malformed PEL program, or missing table field can leave IC-CAP unresponsive and require a restart, and it names concrete verification steps.

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 longer than average but every sentence earns its place: the core action is front-loaded, and the numbered safety checks are structured and directly actionable. The warning about IC-CAP becoming unresponsive justifies the length.

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 no annotations and no output schema, the description covers the critical context: required preconditions, failure modes, and verification tool paths. It does not describe what a successful execution returns, but for an execute-style tool with only two documented parameters, the existing guidance is largely sufficient.

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 coverage is 100%, so the schema already documents transform_path and run_async. The description adds meaningful semantics beyond the schema by explaining what can and must be verified about the transform_path target, including program content and built-in transform table fields.

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 opens with 'Execute/Run a Transform,' a specific verb and resource that clearly identifies the tool's action. It is distinct from sibling tools like transform_create, transform_get_function, and setup_simulate by focusing on execution of an existing Transform.

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 provides clear pre-execution context: verify existence, function type, program content, and required fields before running. It effectively says 'do not execute unless these checks pass,' giving conditional usage guidance, though it does not explicitly contrast with alternative execute-type tools like macro_execute.

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