tealfabric_execute_process

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

No annotations are provided, so the description carries the full burden: it does not say whether execution is synchronous or asynchronous, what side effects occur in downstream connectors, whether it is idempotent, or what a failure looks like. Only the 'optional input' detail hints at behavior at all.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is a function of under-specification rather than precision.

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 tool with a free-form nested input payload, no output schema, and zero annotations, the description omits what execution returns, whether results are polled, and how the input object maps to process variables. The agent is left guessing about the most consequential aspects of the call.

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 100%, so both process_id and the nested input object are already documented in the schema; the description's 'optional input' only restates the optionality. Baseline 3 applies since the schema does the heavy lifting, though the free-form nature of the nested input object is not elaborated anywhere.

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 (Execute) and resource (a Tealfabric process), so the basic action is clear. But it does nothing to distinguish this from the many sibling tools that also 'execute' or 'run' things (e.g. tealfabric_execute_integration), and 'Tealfabric process' just echoes the namespace rather than explaining what a process is.

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?

There is no guidance on when to use this versus tealfabric_execute_integration, tealfabric_get_process, or tealfabric_list_processes, and no prerequisites (permissions, process state, whether steps must exist). The agent has to infer everything about appropriate invocation from the name alone.

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