List storeys

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

Annotations already declare readOnlyHint=true and openWorldHint=falsearke; the description adds useful behavioral context by exposing the exact row schema and the concept of a selected storey that other tools depend on. There is no contradiction.

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 dense sentence that leads with the core output format and then provides the one essential behavioral note about selection and editing. No wasted words.

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 listing tool with an output schema and read-only annotations, the description is fully sufficient: it names the fields, explains selection relevance, and points to the editing sibling.

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)Skip, so there is little to explain. The description adds value by enumerating the returned columns, which is more meaningful than the empty input schema alone.

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 defines the tool's output as storey rows with specific fields, and the title 'List storeys' reinforces the listing purpose. It also distinguishes this from edit_levels by noting that other tools act on the selected storey.

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?

It provides clear context that this tool returns storey rows and that edits should go through edit_levels, naming the appropriate sibling alternative. However, it does not explicitly state conditions like 'when you need to see available storeys' or exclude non-list use cases.

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