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. It only states that a process is created, but does not disclose side effects, permissions required, idempotency, or what happens to existing processes. For a create action, this is a minimal disclosure that leaves behavioral expectations largely unspecified.

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 sentence, concise and front-loaded with the core action and purpose. However, it is so brief that it omits necessary detail; while it earns its place for purpose clarity, it sacrifices completeness for brevity.

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 three required parameters and no output schema, the description should explain parameter roles and perhaps return behavior. It does neither. The description only clarifies the 'what' and 'why', leaving the 'how' (parameter usage) and 'what to expect' completely unaddressed. Given the tool's simplicity, a bit more context would be expected.

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 0% for all three parameters (business_id, name, description), and the description provides no additional meaning for any of them. The description does not compensate for the schema's lack of doc comments, so an agent has to infer parameter semantics purely from their names. This is a significant gap for a tool with required 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 states a specific verb ('Create'), a resource ('business process'), and the intent ('to evaluate for automation'). This clearly distinguishes it from siblings like create_business or save_discovery_answer, which target different entities.

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 tool versus alternatives, nor any exclusions or prerequisites. The description does not mention conditions under which another tool (e.g., create_business) would be more appropriate. An agent would have to infer usage from the name and schema alone.

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