list_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 of behavioral disclosure. It states the tool lists all schedulers, which implies a read-only operation, but it does not mention any additional behavioral traits such as ordering, filtering, or potential errors. For a simple list it is acceptable, but the description is minimal and lacks explicit statement of non-mutating behavior.

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 with no redundancy. It front-loads the action and resource, and every word contributes to the meaning. Perfectly concise.

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 tool has no parameters and an output schema is present (as indicated by context signals), the description sufficiently covers what an agent needs to know to invoke it correctly. No additional context about return structure is needed since it's provided by the output schema. The description is complete for a zero-argument listing tool.

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 zero parameters, so the description does not need to explain parameter semantics. Baseline for 0 params is 4, and the description adds no unnecessary detail. The schema already indicates no arguments, so the description is adequate.

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 verb 'list' and the resource 'available noise schedulers used for image generation'. It is specific and immediately distinguishes this from sibling tools like list_models or generate_image. There is no ambiguity about what the tool does.

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 its usage context (when listing schedulers for image generation) but does not explicitly state when to choose this over alternatives or mention any exclusions. Since this is a simple list operation with no alternative that overlaps in function (schedulers vs models), the implied usage is sufficient for an agent to select it correctly.

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