list_preview_runs

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

No annotations are provided, so the description carries full burden. It fails to disclose ordering, pagination, default behavior for limit, or whether the operation is read-only. Only states 'recent preview runs' without clarifying recency criteria.

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 (9 words), but it sacrifices necessary information for brevity. For a simple list tool, this is minimally adequate but could be expanded slightly without losing conciseness.

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?

Given the output schema exists (though not shown), the description might be partially complemented, but it still lacks essential context like sorting, filtering scope, or relationship to other preview tools. The single parameter and lack of details make it incomplete for effective use.

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 does not explain the 'limit' parameter beyond its name. The schema provides a default but no semantic meaning, leaving agents uninformed about its effect (e.g., max records, pagination).

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 clearly states the action ('list') and resource ('preview runs'), with qualifiers 'recent' and 'under the configured artifact root'. It distinguishes from sibling tools like 'render_preview' which likely produce a visualization, though no explicit differentiation is given.

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 on when to use this tool versus alternatives (e.g., 'get_preview_manifest' for manifest details, 'render_preview' for rendering). The description does not mention contexts, prerequisites, or exclusions.

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