list_states

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

With no annotations, the description must disclose behavioral traits itself. It only says 'List all states', but does not mention whether all states are returned at once, if pagination is supported, or any permission requirements. The output schema exists but the description adds no behavioral context.

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, clear sentence that is front-loaded with the key action and resource. No unnecessary words or filler. It is appropriately brief for the tool's simplicity.

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?

The description is minimal but the tool is simple. An output schema exists, so return value description is not needed. However, it lacks mention of default parameters, ordering, or any limitations. For a list tool, it would benefit from noting that states are listed without filtering or that params can be used for pagination or sorting.

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%, so the schema already describes both parameters (project_id and optional params). The description adds no additional meaning beyond the schema's descriptions. According to guidelines, baseline is 3 when coverage is high and description adds no extra value.

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 'List all states in a project.' clearly specifies the action (list), resource (states), and scope (in a project). It distinguishes from sibling tools like 'create_state', 'update_state', and 'retrieve_state' which have different purposes.

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?

No guidance is provided on when to use this tool versus alternatives such as 'retrieve_state' for a single state, or 'list_cycles' for other resources. There is no mention of prerequisites, filtering options, or when to avoid using it.

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