list_experiments

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

With no annotations and no output schema, the description carries the full behavioral burden. It hints at the return shape ('parameters and named variants') but says nothing about ordering, pagination, whether it is a read-only safe operation, or any auth requirement. That is thin for a tool with zero structured behavioral coverage.

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?

A single short sentence fragment with no filler or redundancy. It is efficient, though being a fragment rather than a front-loaded sentence with a clear verb slightly weakens the opening.

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 tool with no annotations and no output schema, the description supplies only the rough content of the listing. It omits ordering, pagination, and how the result set differs from sibling list tools, leaving an agent to guess at runtime behavior.

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 parameters, so there is nothing to document and the baseline of 4 applies. The description does not need to explain arguments and correctly does not attempt to.

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 is a noun phrase ('Experiments ... with their parameters and named variants') rather than a verb+resource statement, though the name list_experiments implies enumeration. It does convey scope (shipped experiments plus the caller's own, including parameters and variants), which distinguishes it somewhat from get_experiment, but it never states that it retrieves a collection.

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 explicit guidance on when to call this versus get_experiment, catalogue, or list_runs, nor any mention of prerequisites or filters. The scope hint ('shipped and the person's own') implies a use case but leaves the agent to infer the alternative-tool routing.

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