alterios_fast_live_bulk_process

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

Lacks annotations, so description must disclose behavior. Only mentions 'plan or start' and 'verified', but does not explain what verification entails, whether it executes immediately, or if it is asynchronous. No details on side effects or consequences.

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 very short (one sentence), which is concise but sacrifices essential details. It is not efficiently informative given the tool's complexity.

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?

With 20 parameters, 7 required, no annotations, no parameter descriptions, and a minimal description, the tool is severely incomplete. The agent lacks critical context to use it correctly.

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%, meaning no parameter descriptions. The description adds no parameter information despite 20 parameters, including complex ones like 'delivery_evidence'. The agent cannot understand parameter purposes from the description alone.

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?

Description states it plans or starts a BPMN process for selected content rows, which is clear. However, it does not differentiate from the sibling 'alterios_start_process', which likely starts a single process; the 'bulk' and 'live' aspects are implied by the name but not explained.

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?

No guidance on when to use this tool vs. alternatives like alterios_start_process. No prerequisites or scenarios provided. The agent is left to infer usage from the name.

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