fastmean_list_runs

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — that these runs persist across restarts — but says nothing about ordering, completeness of the list, or pagination behavior when more than the limit exist.

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 with no padding, but it front-loads the vague 'Find' rather than the actual action of listing stored runs. Efficiently sized yet under-informative rather than tight.

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 values need not be spelled out, and annotations cover safety. Still, for a list tool the limit/pagination contract and any ordering or filtering assumptions are missing, leaving an agent guessing about result-set size.

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% for the single 'limit' parameter, so the description is the only place semantics could be supplied and it supplies none. No mention of the default (20), the cap (100), or whether truncation signals more results.

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 verb 'Find' is soft for what is clearly a listing operation, and the resource is described only by enumeration ('persisted calculations, created diagrams and preview runs'). It conveys the domain, but nothing distinguishes it from siblings like fastmean_get_result or fastmean_preview, which also surface stored results.

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 use this versus fastmean_get_result, fastmean_preview, or fastmean_status. The phrase 'after restart' hints at a recovery/discovery scenario but is never stated as a usage condition or exclusion.

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