List Slices

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

With no annotations provided, the description carries the full burden. It discloses that slices are not stored data, but filters over entries, and explains the behavioral implication of an empty slice. This adds valuable context beyond the schema.

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 concise with three sentences, each serving a distinct purpose: stating the function, clarifying behavioral nuance, and providing usage advice. No extraneous 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?

The description covers the core functionality, behavioral details, and usage context. However, it does not explain what happens when projectId is omitted (since it's not required) or specify the output format beyond having an output schema. Nonetheless, for a list tool with an output schema, this is adequate.

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?

Schema coverage is 100% with a single parameter 'projectId' described simply as 'Project id'. The tool description does not add any additional meaning or context to this parameter, such as its effect on output or whether it's optional. It meets the baseline but provides no extra value.

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 that it lists built-in and custom slice views, clarifying that slices are filters over entries, not separate data. It also explains the meaning of empty slices, distinguishing from missing slice definitions. This effectively differentiates it from related tools like get-slice.

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 explicitly instructs to use this tool before get-slice to pick a sliceId, providing clear context. While it does not delineate when not to use it or list alternatives, the usage direction is strong.

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