list_timeclock

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 explains what time clock events represent (clock-in/clock-out) but fails to disclose read-only safety, pagination behavior details, or what the response structure looks like (critical given no output schema exists).

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 with zero waste. The first sentence establishes the action and resource; the second provides domain context. Appropriately front-loaded and sized for the tool's complexity.

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?

Adequate for a filtered list operation with 100% schema coverage, but gaps remain due to the lack of output schema and annotations. The description should ideally specify what data is returned (e.g., timestamps, event types) to compensate for the missing structured output definition.

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%, establishing a baseline of 3. The description adds semantic context by mentioning 'technician' and 'shop staff,' which helps clarify the expected values for the userId parameter, but does not elaborate on date format specifics or pagination usage beyond the schema definitions.

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 uses the specific verb 'List' with the resource 'technician time clock events' and clarifies the domain as 'clock-in/clock-out for shop staff.' It implies differentiation from generic user listing tools (like list_users) by focusing on time-tracking events, though it does not explicitly contrast with siblings like list_labor.

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 provided on when to use this tool versus alternatives such as list_labor or get_user. It does not mention prerequisites (e.g., needing a valid locationId) or suggest which filters are most effective for common use cases.

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