filter_shifts

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

With no annotations, the description must disclose behavioral traits. It only states the action (list shifts) with filtering, but fails to mention whether it is read-only, any side effects, permission requirements, or response behavior (e.g., pagination). This is insufficient for safe invocation.

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 sentence with no wasted words, but it is overly terse. It lacks structure (e.g., separate lines for purpose and details) and omits critical information, making it insufficiently informative despite its brevity.

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 8 parameters and no annotations, the description is incomplete. It does not explain how text and duration filters relate to the required start/end parameters, nor does it clarify the behavior of optional filters. The presence of an output schema partially offsets missing return info, but input-side gaps remain.

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 description coverage is 0%, so the description should compensate. It mentions 'text and duration filters' but does not map these to specific parameters (e.g., title_contains, min_hours). While parameter names are somewhat self-explanatory, the description adds no extra meaning beyond the schema itself.

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 'List shifts matching text and duration filters' clearly states the tool's verb and resource, and hints at filtering capabilities. However, it does not differentiate from siblings like list_shifts or shifts_on_date, lacking specificity about which text fields are filtered.

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 usage guidelines provided. The description does not specify when to use this tool versus other shift-listing siblings, nor does it mention any contextual prerequisites or exclusions.

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