passgage_list_user_shifts

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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It only mentions 'optional filtering and pagination', which is more about features than behavior. It does not explicitly state that this is a read-only operation, nor does it describe return format or side effects, leaving a significant transparency gap.

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, concise sentence that front-loads the verb and resource, then briefly notes the key features. Every word earns its place, and there is no unnecessary repetition or verbosity.

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 is minimal but adequate for a simple list operation. However, without annotations or an output schema, it leaves some gaps: it doesn't clarify what a 'user_shift' is, nor does it describe the returned data structure. Given the similar pattern across sibling list tools, the description is technically sufficient but could be more informative.

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 schema already provides complete descriptions for all three parameters (page, filters, per_page), so the baseline is 3. The description's mention of 'optional filtering and pagination' merely echoes the schema without adding meaningful new semantic detail.

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 specifies the verb 'List' and the resource 'user_shifts', making its core purpose evident. However, it does not explicitly distinguish this tool from sibling tools like 'list_shifts' or 'list_users', which could lead to confusion about the exact scope.

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 implies usage for listing user shifts, but it provides no explicit guidance on when to use this tool versus alternatives. There are no stated contexts, prerequisites, or exclusions to help the agent choose correctly.

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