yaaif_plan_execution_list

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

No annotations are present, so the description must convey behavioral details. It only states the action without disclosing that it is read-only, what it returns, or any side effects. While it implies a list operation, it does not explicitly state that it does not modify data or what the response structure is.

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 with no filler. It is front-loaded and gets straight to the point, making it easy for an agent to parse quickly.

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 list tool with no parameters and no output schema, the description is adequate but minimal. It does not mention that the operation returns a list of saved executions, nor does it hint at any filtering or sorting. Given the tool's simplicity, this is a minor gap, but it could be improved by stating the return type or clarifying scope.

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 there is nothing to describe beyond what the schema already indicates. With no params, the baseline is 4, and the description adds no unnecessary detail about parameters, which is appropriate.

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 saved plan executions.' clearly states the action (list) and the resource (saved plan executions). It distinguishes from siblings like yaaif_plan_execution_get (single) and yaaif_plan_execution_save (create) by its plural and specific scope. An agent can easily identify this as the listing operation.

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 about when to use this tool versus alternatives. There is no mention of typical use cases, prerequisites, or that it returns all saved executions. The description does not contrast with yaaif_plan_execution_get or other list operations.

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