Create Business Process

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the agent knows this is a write operation. The description adds the relationship to Record Types and the ordering constraint, providing useful behavioral context. It does not disclose return values or auth requirements, but with annotation coverage this is acceptable.

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 two sentences, front-loaded with the action and resource, with no filler. Every sentence earns its place.

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 description explains the core function and a key dependency, and the schema covers parameters. However, with no output schema, it does not state what is returned upon success, and it does not mention permissions or side effects beyond the stated relationship. Given the tool's moderate complexity, this is a minor gap.

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 schema covers all six parameters with descriptions, so the baseline is 3. The description adds conceptual meaning by mapping values to picklist values and listing the valid objects. It does not add syntax details beyond the schema.

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 uses the specific verb 'Creates' and names the resource 'Business Process' with explicit object types (Opportunity, Lead, Case, Solution). It clearly distinguishes this from sibling create tools like sf_create_approval_process by explaining it defines picklist values for Record Types.

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 includes a clear temporal prerequisite: 'Must be created before assigning to a Record Type.' This provides useful context on when to invoke the tool. However, it does not name alternatives or explicitly state when not to use it.

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