tenki_list_volumes

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar for extra disclosure is lower. The description adds useful behavioral context beyond annotations by noting the default workspace behavior and pagination support.

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, front-loaded sentence with no filler. It communicates the core action, the scope, a default behavior, and pagination in minimal 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 simple read-only listing tool with fully documented parameters and supporting annotations, the description is complete enough for an agent to call it correctly. No output schema is present, but the return type is strongly implied by 'list volumes.'

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?

All three parameters are described in the schema (100% coverage), so the description does not need to compensate. The description's mention of the default first workspace and pagination adds no meaning beyond the schema descriptions already present.

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 starts with a specific verb ('List') and identifies the resource ('persistent volumes in a workspace'), which clearly distinguishes it from sibling tools like tenki_list_sandboxes or tenki_get_volume. The parenthetical about the default workspace adds further precision.

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 makes clear it is for listing volumes in a workspace and mentions the default workspace and pagination, giving an agent enough context to select it over volume mutation tools. It does not explicitly mention when not to use it or name alternatives, but the resource scoping is strong.

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