processDefinition_deploy

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

Discloses return values ('deployment metadata and deployed definition keys') which helps given the lack of output schema, but omits critical behavioral details required for a mutation tool without annotations: idempotency, handling of duplicate definitions, validation errors, or side effects on the server.

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?

Three sentences efficiently structured: action definition, input requirements, and return value. No redundant phrases, though the null title wastes the opportunity for a concise label.

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 deployment operation (high complexity, no annotations, no output schema), the description is insufficient. It lacks versioning behavior, error handling patterns, and the critical distinction from generic deployment siblings necessary for safe agent operation.

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?

With an empty input schema (0 parameters), the description attempts to compensate by listing three expected inputs ('BPMN or DMN XML', 'filename', 'deployment name'), but fails to explain their formats, relationships, or validation rules. The disconnect between described parameters and empty schema creates ambiguity.

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?

Specific verb 'Deploy' and resource 'BPMN process definition' are stated, plus the target system 'Operaton'. However, it mentions handling DMN XML as well, which overlaps with the `decision_deploy` sibling without clarifying the distinction, and the null title weakens identification.

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?

Lists required inputs (XML, filename, deployment name) but provides no guidance on when to use this tool versus `deployment_create` or `decision_deploy`, nor prerequisites like authentication or permissions needed for deployment.

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