list_states

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

Discloses the 5-minute cache ('cached 5 min') and explains the return structure (id, name, group, color, sequence). No annotations exist, so this carries the full burden; it covers caching and data semantics, though it omits any error or rate-limit details.

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?

Two concise sentences front-load the main action, then provide field detail and usage. No wasted words.

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 an output schema present and zero parameters, the description is complete: it covers purpose, caching, field enumeration, and the exact reason to call it. The output schema handles precise return types.

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?

Tool takes no parameters, so the description has no parameter burden. Baseline of 4 applies, and the description adds context by explaining how to use the returned data, which is helpful.

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?

States the exact action and resource: 'List workflow states for the configured project.' It also clarifies the value for LLMs (mapping status_group to state_id), which differentiates it from sibling tools like list_tasks or list_members.

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?

Explicitly states when to use: 'LLMs need this to map status_group → state_id when creating or updating tasks.' This gives a clear invocation context and ties it to workflows.

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