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

Annotations declare readOnlyHint=true, and the description goes beyond that by disclosing the returned record shape (StartTime/EndTime unix, StartTimeLocalized, Employee as 0 or null when open, OperationalUnit, Published, Open, Cost, _DPMetaData) and the underlying API endpoint. No output schema exists, so this return-shape disclosure is genuinely load-bearing. It does not add permission or rate-limit detail, and the 'POST .../QUERY' endpoint note is an implementation detail rather than a behavioral trait, but the safety profile plus return structure is well covered.

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, zero waste. The search scope and filter axes are front-loaded in sentence one; the return-field inventory and API reference follow. Nothing is padding, especially since the field list substitutes for a missing output schema.

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 8 all-optional parameters and no output schema, the description does the heavy lifting on return values and filter axes, which is exactly what an agent needs to construct a query. It stops short of describing pagination/limit behavior (max cap, next_start chaining) beyond what the schema states, so it is strong but not fully complete.

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 100%, so baseline is 3. The description's filter enumeration (time window, employee, area, published/open) maps onto from/to, employee_id, area_id, published, and open, and '(0 or null when open)' clarifies the Employee value convention, but it adds no format or syntax detail beyond what the schema already states for each parameter.

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?

States a specific verb and resource ('Search the roster (scheduled shifts)') plus the four filter dimensions. An agent can distinguish it from deputy_get_shift (single shift), deputy_create_shift, and deputy_publish_shifts without opening any schema.

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?

Usage is implied by the filter-oriented phrasing, and the Deputy endpoint (Roster/QUERY) hints at a query operation, but there is no explicit when-to-use guidance and no named alternative such as 'use deputy_get_shift for a single shift by id'. Adequate but leaves routing to inference.

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