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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the useful behavioral detail that only *trained* artifacts (models/filters, .pkl) are returned, implying intermediate files are excluded. It says nothing about ordering, pagination, or what happens when a run produced no artifacts.

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?

One short sentence, front-loaded with the key qualifier 'Trained artifacts' and an illustrative extension example. No waste, though it is arguably too terse to carry usage or behavioral context.

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?

An output schema exists, so return structure need not be explained, and the safety annotations cover the mutation question. Still, for a listing tool whose value depends on knowing scope (trained only? sorted? downloadable?) and its relationship to download_artifact, the description leaves meaningful gaps.

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?

With a single parameter at 100% schema description coverage, the schema already defines execution_id as 'Run whose artifacts to list.' The description adds no format, source, or lookup guidance beyond that, so the baseline of 3 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 identifies the resource as trained artifacts (models/filters, e.g. *.pkl) saved by an execution, which clarifies what kind of files are returned. However, it never states the verb 'list' and does not explicitly contrast with execution.download_artifact or execution.results, so the agent must infer the operation from the name and title rather than the description.

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?

There is no guidance on when to call this versus siblings such as execution.download_artifact (to fetch contents) or execution.results (for metrics/outputs). The agent gets no exclusions or alternative routing, only an implied 'use this to see what was saved'.

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