list_executions

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does reveal that results are compact partial/completion summaries rather than full execution records, but it does not mention read-only behavior, pagination semantics, ordering, or what 'durable' means in this 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 front-loaded sentence with no filler. It communicates the action, the resource, and the nature of the returned summaries efficiently.

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 simple paginated list tool with an output schema, the description covers the core behavior sufficiently. It lacks details like ordering or total count, but those are likely already represented in the output schema, and the parameter surface is minimal.

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 description coverage is 0%, and the description adds no meaning for the limit and offset parameters. The parameter names and schema constraints are self-explanatory enough for simple pagination, but the description does not compensate for the lack of schema descriptions as required when coverage is low.

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 states a specific verb and resource: 'List durable executions'. It also identifies the result shape as 'compact partial/completion summaries', which clearly distinguishes this listing tool from siblings like get_execution or get_execution_output that imply retrieving a single execution or its full output.

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 implies this tool is used when a list of executions with summaries is needed, but it does not provide explicit when-to-use guidance or contrast with alternatives such as get_execution, get_execution_output, or list_captures. The usage context is clear but only implied.

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