tealfabric_create_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 of behavioral disclosure. It discloses the primary side effect ('Create') and the return value ('new process_id'), but does not mention important behavior such as default status, whether creation is idempotent, required permissions, or side effects on related entities. For a mutation tool with no annotation coverage, this is a notable gap.

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, front-loaded sentence that immediately states the action, resource, and return value. Every word earns its place, and there is no redundant repetition of the tool name or title.

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 tool has 12 parameters, a nested object in configuration, no output schema, and no annotations, yet the description only states the basic creation action and return value. Most of the schema properties lack descriptions, and the description provides no context on required fields, defaults, parameter semantics, or how the created process relates to the process lifecycle. This is far from complete for an agent to use the tool correctly.

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 only 8%, and the description does not compensate by explaining any of the 12 parameters. The only described parameter behavior comes from the schema's name field and status enum, while the description itself adds zero input semantics. With such low coverage and no compensating description, an agent is left without meaningful guidance for most parameters.

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 a specific action ('Create') on a specific resource ('a new Tealfabric process') and notes the return value ('Returns the new process_id'). It is not a tautology and distinguishes the tool from unrelated siblings like connectors and documents, though it does not explicitly contrast with process-related siblings like update_process or create_process_step.

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 when to use the tool: when a new process needs to be created. However, it provides no explicit guidance about when not to use it or what alternatives exist, such as using create_process_step for steps or update_process for modifying an existing process. The usage context is clear but not enriched with exclusions or decision rules.

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