list_task_states

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

The readOnlyHint annotation already covers safety, so the description does not need to repeat that. It adds the useful conceptual distinction that task state is separate from Kanban stage, but does not disclose additional operational behaviors such as whether the list is sorted, paginated, or reflects real-time changes beyond the word 'live'.

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 entire description is one concise sentence that states the action, the resource, and the key distinguishing concept. It is front-loaded and contains no filler or redundant 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?

For a zero-parameter read-only list tool with an output schema present, the description provides sufficient context. The clarification about Kanban stage separation is the main piece of domain knowledge needed to use the tool 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 description has no parameter semantics to convey. With an empty input schema, the baseline of 4 is appropriate; no additional parameter explanations are needed.

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 ('List') and resource ('live Odoo 17 task state keys'), making the tool's purpose immediately clear. It also explicitly distinguishes task state from Kanban stage, which separates it from sibling tools like list_project_stages and set_task_state.

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 clearly implies this tool is for retrieving task state keys rather than Kanban stages, providing a useful when-not context. It does not explicitly name an alternative tool, but the sibling list includes obvious related tools and the distinction is enough to guide selection.

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