fluig_form_list

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the filter capability and returned fields but lacks details on pagination, ordering, error handling, or the effect of no filter. For a list operation, such information is important for correct invocation.

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 one sentence that concisely states the action, returned fields, and optional filter. There is no unnecessary text, and it is front-loaded with the essential information.

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?

The tool is simple with one parameter and no output schema. The description covers the basic functionality but does not specify the response format (e.g., array of objects) or behavior when no filter is applied. For a list tool, additional completeness would be beneficial but is not severely lacking.

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 100% for the single parameter. The description adds 'substring' context, which matches the schema description. No additional meaning beyond the schema is provided, so the baseline score of 3 is appropriate.

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 the verb 'List' and the resource 'forms', and specifies the returned fields (documentId, version, description, dataset). It also mentions the optional substring filter, which helps distinguish from other form-related tools like fluig_form_full (which likely retrieves a single form). However, it does not explicitly contrast with siblings, so a score of 4 is appropriate.

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 versus alternatives, such as fluig_form_full or fluig_dataset_list. It does not specify prerequisites, limits, or when not to use it. The description only states the basic function with minimal context.

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