list_samplers_and_schedulers

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a dict with 'samplers' and 'schedulers' lists, which is sufficient for a read-only list operation. No side effects or permissions are mentioned, but none are expected for this simple list tool.

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 exactly two sentences: one for the action and one for the return format. It is free of unnecessary words and front-loads the core purpose.

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?

The tool is extremely simple—no parameters, no complex behavior, and an output schema exists. The description fully covers what the agent needs to know: what it lists and the shape of the result. Nothing further is required.

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 tool has 0 parameters, and the input schema is empty. Per the rubric, 0 parameters yields a baseline of 4, and the description does not need to elaborate on parameter semantics that do not exist.

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 tool lists all available sampler algorithms and noise schedulers, using a specific verb and resource. It distinguishes from sibling list tools like list_models and list_files by naming the exact domain.

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?

The description implies usage for discovering available samplers/schedulers but provides no explicit when-to-use or alternative context. Since it is a distinct listing tool, the purpose is obvious, but there is no guidance on when not to use it or when to prefer a different tool.

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