ak_list_runs

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the basic read-only intent ('list') but does not disclose ordering, recency bounds, default limits, result shape, or any filtering behavior. It is minimal rather than misleading.

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?

'List recent runs.' is three words with no filler, fully front-loaded, and appropriately sized for a zero-parameter tool. Every word earns its place.

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 zero-parameter list operation, the description is technically sufficient to invoke, but 'recent' is vague and there is no indication of output shape, ordering, or limits. With no output schema and no annotations, important contextual information is left to inference.

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 has zero properties and 100% coverage, so the absence of parameters is already fully clear. The description adds no parameter detail, but none is needed; baseline 4 applies.

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 ('runs'), so an agent can tell this is a listing operation rather than a retrieval or mutation. It is implicitly distinguished from siblings like ak_get_run (list vs. get) and ak_list_projects/ak_list_assignments (runs vs. other entities), though 'recent' is left undefined.

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 explicit 'when to use' or 'when not to use' guidance is given, and no alternative tools are mentioned. The intended use is implied by the description: call this when you need a list of recent runs.

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