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

Annotations already declare readOnly/openWorld/no-destructive, so the bar is lower; the description still adds real context by disclosing that the source is a read-only OData warehouse refreshed nightly, so today's punches may be missing until tomorrow. It also documents ordering ('newest first') and the pagination loop via next_skip.

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?

Front-loaded with what the tool returns and how to filter, then the freshness caveat and pagination note; every sentence earns its place. The trailing 'GET /odata/DwTimePunches' endpoint detail is the only borderline filler.

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 still names the returned fields and explains that next_skip comes from the previous reply, which is enough to drive pagination correctly. Only the shape of the response envelope (e.g. presence of a next_skip field name) is left implicit.

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 every parameter is already documented in the schema; the description's restatement of date/person/location filters and skip/next_skip adds little beyond it. Baseline 3 applies since the schema carries the load.

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 ('List raw clock punches') and enumerates the returned fields, which separates it in spirit from time_records and shifts. It does not explicitly name those siblings, so an agent must infer the boundary rather than being routed.

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?

Offers filtering guidance ('by date range (UTC days), person or location') and pagination instructions, plus a useful freshness caveat, but never states when to prefer this over exaktime_list_time_records or exaktime_list_shifts, which are the closest alternatives.

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