keel_list_tasks

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

No anotations are provided, so the description carries the burden. It goes beyond a simple statement by listing exact output fields and status enum values. It doesn't discuss pagination or ordering, but for a read-only list with no parameters, this is adequate transparency.

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 a single, front-loaded sentence. It conveys the operation, resource, and output structure without wasted words, making it easy to scan.

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?

With no output schema, the description provides the complete return-value shape, including field names, status values, and assignee fields. For a zero-parameter listing tool, this is sufficient for an agent to call it 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?

The tool has zero parameters, so the baseline is 4. The description need not explain parameter semantics, and the input schema confirms no parameters exist.

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 opens with a specific verb, 'List', and a clear resource, 'workspace compliance tasks'. It enumerates the item's fields, making the tool's purpose unambiguous and distinguishing it from sibling list tools targeting different resources.

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 clear context: use this tool to retrieve workspace compliance tasks. It doesn't explicitly mention alternatives, but the list of sibling tools makes the distinction obvious, and there is no competing task-listing tool.

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