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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the result is null when the person is not clocked in and that a field worker sees only their own running clock, but it does not state read-only behavior, permission requirements, or what happens when person_id is omitted.

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 two short sentences, front-loads the current-clock resource, and adds only the null-state and visibility details. There is no redundant or filler text.

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?

An output schema exists and the tool is simple, but with no annotations and 0% parameter description coverage, the definition should clarify whether it returns the caller's clock or a specified person's clock. It covers null behavior and visibility but leaves key invocation details 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 0%, so the description needed to explain shop_id and person_id. It only alludes to the fields through 'in a shop' and 'a person's', without stating that person_id is optional, whether it defaults to the caller, or how shop and person filtering interact.

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 identifies the resource as a person's current/running clock in a shop and states that it is null when they are not clocked in. It lacks an explicit retrieval verb and does not name a sibling, but the resource and state are specific enough to distinguish it from timesheets_list, timesheets_clockIn, and timesheets_clockOut.

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?

The description gives no explicit when-to-use or when-not-to-use guidance and does not mention alternatives such as timesheets_list or timesheets_clockOut. At best, checking whether someone is currently clocked in must be inferred from the description.

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