kaiten_list_automations

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

With no annotations provided, the description carries the full responsibility for conveying safety and side effects. The verb 'List' signals a non-mutating read operation and the space scoping clarifies scope, but the description does not disclose pagination, ordering, output shape, or any authentication requirements.

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?

One short, front-loaded sentence communicates the essential purpose with no filler. Every word contributes to the meaning.

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 single-parameter list operation, the description plus schema are sufficient for an agent to call the tool correctly: it knows the required space_id and that the result is the set of automations for that space. The lack of an output schema means return details are not required, though a note on response format would make it fully complete.

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 schema already documents space_id at 100% coverage, so the baseline applies. The description reinforces that the operation is scoped to a specific Kaiten space, but it adds no format, validation, or behavioral details beyond the schema.

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 ('automations'), and scopes the action to 'a Kaiten space'. This clearly distinguishes it from single-item automation tools like get_automation, update_automation, and delete_automation.

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 phrase 'List all automations' makes the tool's role as a collection-level query clear enough, and it is implicitly the right choice when the full set of automations in a space is needed. However, it does not explicitly name alternatives or describe when to prefer get_automation or other list tools.

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