List Redfish tasks

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

The description discloses the return structure ('Object with TaskService entries under tasks'), the list wrapping format ({items, total, truncated}), and the effect of include_details. This adds behavioral context beyond the annotations, which already declare read-only/idempotent/non-destructive.

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?

Three sentences: purpose, return format, and a concrete example. No wasted words; information is front-loaded.

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's simplicity, full output schema, and rich annotations, the description covers all critical aspects: what it lists, the return shape, truncation behavior, and an example invocation. It is complete for an agent to select and invoke 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 coverage is 100% with both parameters (endpoint and include_details) already well-described. The description reinforces include_details via the example and first sentence but adds no new parameter-level meaning beyond that.

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 uses a specific verb+resource ('List TaskService task members') and clarifies the optional behavior (including full payloads). It distinguishes itself from sibling tools like get_task by being plural and scoped to TaskService. The example further clarifies intent.

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 implies usage (list all tasks, optionally with details), but it does not explicitly state when to prefer this over sibling tools like get_task, nor does it mention exclusions or alternatives. The example demonstrates usage, providing some contextual guidance.

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