Operaton MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It documents the return fields (id, type, retries, dueDate, exceptionMessage) which compensates for the missing output schema. However, it omits critical list-operation behaviors: pagination, result limits, and whether this reads runtime or historic jobs. The 'List' verb implies read-only, but this is not explicitly confirmed.

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 tightly written sentences with no wasted words. The first establishes the operation and filters; the second documents return values. Information is front-loaded with the verb and resource.

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?

While the return fields are documented (helpful given no output schema), the description lacks essential context for a list tool: pagination behavior, maximum results, and the distinction between runtime and historical job queries. Given the presence of history_listJobLogs in siblings, clarifying this scope would be necessary for completeness.

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?

There is a significant discrepancy: the description details 'optional filters' (process instance, job definition, etc.), but the input schema is completely empty (properties: {}). This mismatch could mislead the agent into attempting to provide filter parameters that the schema does not support, potentially causing invocation errors or hallucinated arguments.

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 identifies the action ('List jobs') and the resource, and distinguishes this from sibling tools like job_get (singular retrieval) by emphasizing the list operation with filtering capabilities. It effectively conveys that this tool retrieves multiple job records.

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 fails to clarify when to use this tool versus siblings like job_get (for single job retrieval), job_count (for aggregation), or history_listJobLogs (for historical vs runtime jobs). No guidance is provided on when filtering is necessary versus retrieving all jobs.

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