List Tasks (Dalux Field)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds the note about read-only API and clarifies that typeId is the only server-side filter, which adds useful behavioral context beyond the annotations.

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 plus a note, front-loaded with the purpose. Every sentence provides necessary information without verbosity.

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 4 parameters, present annotations, and no output schema, the description covers essential aspects: return fields, filtering limitation, read-only nature. Slightly lacks explicit mention of pagination behavior (though schema covers maxPages and pageLink).

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%, baseline is 3. The description adds value by enumerating the fields returned (subject, type, workflow state, etc.), which is not in the schema, and explains the typeId filter behavior.

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 'tasks', along with other related items (approvals, safety issues, etc.). It distinguishes from sibling tools like 'dalux_get_task' and 'dalux_list_forms' by specifying the scope.

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?

Description mentions the optional typeId filter as the only server-side filter, providing context on filtering capabilities. It also notes that the API is read-only, but does not explicitly contrast with alternatives like 'dalux_get_task' for single record retrieval.

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