list_cells

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

With no annotations, the description must carry the burden of disclosing behavior. It adds the useful constraint that only session-loaded cells are returned, which helps set expectations. However, it doesn't explicitly state that the operation is read-only, nor does it describe return format or behavior when no cells are loaded.

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 short sentence that immediately states what is listed and the scope, with no filler. This is appropriately concise for a zero-parameter listing 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?

Given there are no parameters and no output schema, the description is mostly sufficient: an agent knows the tool lists the current session's loaded cells. It would be slightly stronger if it indicated the returned form of a cell, but for a simple list call the gap is minor.

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 takes zero parameters, so the schema is already complete; the baseline of 4 applies. The description does not need to explain parameters and introduces no ambiguity.

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 phrase 'The cells loaded in this session' identifies the resource (cells) and the scope (session-loaded), aligning with the verb implied by the tool name. It is distinguishable from load_cell, which is about loading rather than listing. However, it lacks an explicit verb or comparison to siblings.

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?

No guidance is provided about when to use list_cells versus siblings such as load_cell or list_instruments, and there are no exclusions or prerequisites. The 'in this session' qualifier hints at context, but the description never states when to prefer this tool.

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