Get Slice

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

No annotations provided; description should carry burden. Mentions format behavior and filtering, but does not explicitly state it's read-only or disclose any safety/cost implications. Adequate but not thorough.

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?

Two sentences, front-loaded with purpose, no redundancy. Every sentence adds meaning (empty slice, prerequisite call, pagination, filtering).

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?

With output schema present, return values are covered. Description includes key behavioral aspects: empty slice, prerequisite, pagination, filtering, format differences. Missing no critical info given complexity.

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%, but description adds value: clarifies default format, that sliceId can be built-in or custom, and gives examples. Enhances understanding beyond schema.

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 it 'Returns a horizontal project view: filtered entries transformed for agents.' Differentiates from siblings by referencing slices, and explains empty slice behavior.

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?

Explicitly instructs 'Call list-slices first to pick sliceId.' Provides pagination guidance and filtering options, implying when to use. Lacks explicit alternatives but context is clear.

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