fluig_deploy_list

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

No annotations are provided, so the description must cover behavioral traits. It indicates the tool is a read-only list operation (listing processes) and mentions the SOAP service, which hints at potential network requirements. However, it does not state that it is non-destructive or describe any authentication needs, rate limits, or side effects. For a simple list tool, this is adequate but not exceptional.

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 two sentences: one defining the action and scope, the other providing a use case. Every sentence is valuable and there is no redundancy. It is appropriately front-loaded with the primary purpose.

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?

Given the tool has no parameters and no output schema, the description is reasonably complete. It explains what the tool lists (processes available for export/deploy) and gives a practical use case. However, it does not describe the structure of the returned list (e.g., what fields are included), which might leave the agent uncertain about the output format.

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 input schema has no parameters, so schema coverage is trivially 100%. According to guidelines, baseline for 0 parameters is 4. The description does not add parameter meaning because there are none, but it confirms the tool requires no inputs, which is fine.

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 states 'List the processes available for export/deploy', which is a specific verb (list) and resource (processes for export/deploy). It also mentions the underlying SOAP service, adding technical context. However, it does not explicitly differentiate from other list tools in the sibling set, like 'fluig_globalevent_list', though the scope is clear.

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 provides a use case: 'Useful to validate a deploy with a round trip.' This gives some context for when to use it, but it does not offer explicit guidance on when not to use it or alternatives. For example, it does not mention that other tools like 'fluig_process_export_xml' or 'fluig_deploy_process' are for actual export/deploy, not listing.

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