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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavior: the data comes from a read-only OData warehouse refreshed nightly, so today's entries may not appear until tomorrow, and results are ordered newest first. This adds meaningful operational context, though it does not cover rate limits or auth expectations.

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 compact and front-loaded: purpose first, then filters, ordering, source freshness, pagination, and endpoint. Every clause contributes useful context without redundancy.

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 no output schema, the description compensates by listing the main returned fields and explaining pagination via skip/next_skip, plus the warehouse freshness caveat. It is nearly complete for a read-only list tool, though it does not describe the full response envelope.

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 parameter meanings are already fully documented. The description reinforces filtering by date range, person, and location, and notes skip/next_skip pagination and newest-first ordering, but most of this is already present in the 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 states a specific verb and resource — list scheduled shifts — and enumerates the returned fields (employee, start/end, title, cost code, location, notes). This is clearly distinct from generic record listing or actual punch retrieval, even without naming a sibling tool.

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?

It gives useful filtering and pagination guidance (start date range, person, location, skip/next_skip) and a freshness caveat, but it does not explicitly say when to use this tool versus related siblings like time punches or time records. Usage is implied rather than contrasted.

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