passgage_list_shifts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the basic operation and optional parameters, without mentioning auth requirements, default sorting, pagination behavior beyond parameters, or return format.

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 6-word sentence, front-loaded and completely free of filler. It is appropriately concise for a simple list operation.

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 the well-described schema and simple list semantics, the description is minimally adequate. However, without an output schema, it does not indicate what the response contains or how it differs from other list tools, which could affect completeness in a tool-rich environment.

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 descriptions cover 100% of parameters, including the Ransack-style filter example and pagination limits, so the baseline is 3. The tool description adds no extra semantic value beyond repeating that filtering and pagination are optional.

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 the tool lists shifts with optional filtering and pagination, using a specific verb and resource. It does not explicitly distinguish from sibling tools like list_user_shifts or list_shift_settings, but the name itself is fairly specific.

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 given on when to use this tool versus alternatives. It does not mention that get_shift is for individual shifts or that list_user_shifts covers a different resource, leaving the agent to infer usage.

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