List days pending clock-in

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

Declares read-only, lists exclusions, and explains lockedDays behavior. Without annotations, this provides sufficient transparency about what the tool does and does not modify. Lacks detail on output structure.

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?

Four sentences, each with distinct value: purpose, exclusions, read-only, lockedDays explanation, and usage guidance. No fluff or 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?

For a simple tool with one optional parameter and no output schema, the description covers purpose, output content, exclusions, edge cases, and usage instruction. No gaps.

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?

The input schema fully documents the month parameter (format, default). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states it lists workdays with no hours logged, provides exact time ranges, and lists exclusions (weekends, holidays, absences, etc.), effectively distinguishing it from sibling tools like clock_in_days.

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?

Explicitly advises showing ranges to user before clocking in, and states lockedDays cannot be fixed via this tool, implying reporting. However, it does not name the alternative sibling tool (e.g., clock_in_days).

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