list_actions

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

With no annotations provided, the description carries the burden of behavioral disclosure. It communicates that the tool lists recent items and supports filtering, which implies a non-destructive read operation. However, it does not disclose default ordering, pagination, how filters combine, or any rate or access considerations.

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 two short sentences with no filler. The main purpose is front-loaded, and the filtering capability is presented immediately after the core action.

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 optional-parameter list tool, the description is adequate but not complete. It lacks information about the output shape, since there is no output schema, and does not explain what 'recent' means or how to retrieve more than the default number of actions.

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 only 33% because limit has a description but projectName and serviceName do not. The description adds meaning by identifying projectName and serviceName as filters, but it does not clarify whether they can be combined, whether matching is exact or partial, or how limit interacts with filtering.

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 clear verb and resource: list recent deploy actions/builds. It also mentions filtering by project or service, which gives concrete scope. However, it does not explicitly differentiate itself from the sibling get_action_log, leaving some ambiguity about whether this is the right list-style tool.

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 clearly indicates when to use the tool: to view recent deploy actions/builds, with optional filtering by project or service. It provides clear context but does not mention exclusions or alternative tools for related cases, such as retrieving detailed logs via get_action_log.

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