get_fermentation_chambers

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

With no annotations, the description carries the transparency burden. 'List' clearly indicates a read-only, non-destructive operation, and the account scope is stated. It does not disclose return format or pagination, but the operation is inherently simple and the description provides the essential behavioral context.

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 sentence that front-loads the action ('List all fermentation chambers') and includes the scope ('in the RAPT account'). There is zero wasted text, making it ideal for a zero-parameter list tool.

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 description covers the tool's purpose and scope but does not mention the return structure, since there is no output schema. Given the simplicity of a list operation, this is a minor gap; it is adequate but lacks detail on what fields or data the returned chambers include.

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 the baseline score is 4. The description has no parameters to explain, and nothing in the description contradicts or adds to the empty schema. No additional parameter semantics are needed.

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 uses the specific verb 'List' with the resource 'fermentation chambers' and clarifies scope as 'all in the RAPT account.' It clearly distinguishes itself from the singular sibling get_fermentation_chamber by the plural 'chambers' and 'all.'

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 usage is implied: call this when you need a list of all fermentation chambers in the account. It does not explicitly mention alternatives or when not to use, such as using get_fermentation_chamber for a specific chamber, so guidance relies on the tool name and plural form.

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