deploy_process

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states that deploying twice is harmless, which is a useful idempotency trait. However, it does not disclose side effects, required permissions, or what 'deploying' entails beyond the name, leaving significant behavioral context unaddressed.

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?

Two sentences with no fluff. The primary action is stated first, followed by a single relevant caveat about idempotency. Every word 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?

Although an output schema exists, the description lacks key operational context for a deployment action: prerequisites, effects on existing processes, environment assumptions, and how the bpmn_path parameter influences the deployment. The idempotency note is the only behavioral extra.

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 has one parameter (bpmn_path) with 0% description coverage, and the description does not mention it at all. The optional nature and default null are not explained, leaving an agent without any understanding of why or how to use the parameter.

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 a specific verb 'Deploy' and names a resource ('the release process') and destination ('the engine'), making the core action clear. It does not explicitly distinguish itself from siblings like start_release, but the artifact named ('release process') differentiates it enough.

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 mention of when to use this tool versus alternatives such as start_release or list_processes. The only usage hint is the idempotency note, which implies it can be run repeatedly, but no explicit when/when-not guidance is provided.

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