alterios_list_process_tasks

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

No annotations are provided, so the description carries full burden. It indicates read-only behavior but does not disclose permissions, side effects, or other behavioral traits beyond what is stated.

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?

Single sentence, 13 words, front-loads the primary action. Efficient but could benefit from additional structure, such as listing parameters or usage context.

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?

Output schema exists, so return values explanation is not required. However, the tool has 5 optional parameters with no description of how they interact (e.g., mutually exclusive, combined). The description is overly brief for a tool with multiple filtering options.

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%, so description must compensate. It adds meaning for three parameters (process_id, diagram_id, content_id) by mentioning 'by process, diagram, or content context', but does not explain profile or project_id. Baseline for missing coverage is 2, but partial explanation raises to 3.

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 states 'Read process instances and active tasks' which specifies the verb and resource. It distinguishes from siblings like alterios_start_process (write) by indicating read-only nature. However, it does not differentiate from other list tools like alterios_list_profiles.

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. Does not mention when not to use or provide context for filtering choices.

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