get_timesheets_due

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the read implication of the 'get_' prefix. It does not explain what 'due' means, whether results are filtered by date/policy, or whether an empty set is possible.

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?

A single front-loaded fragment with no filler or repetition. It is efficient, though the terseness edges into under-specification rather than serving as genuine concision.

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 annotations and no output schema, the description must supply the context an agent needs, and it does not: the meaning of 'due', the time window, and the relationship to sibling timesheet tools are all absent.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. Baseline 4 applies for a no-argument tool.

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 fragment identifies a resource ('timesheets') and a scope qualifier ('due for the signed-in employee'), which is more than a tautology. However, 'due' is undefined (due today? overdue? due this pay period?), so an agent cannot confidently describe what is returned, and it does not distinguish itself from the sibling get_timesheets/get_rejected_timesheets.

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?

There is no when-to-use guidance and no mention of alternatives, despite several closely related siblings (get_timesheets, get_rejected_timesheets, get_timesheet_profile). The agent is left to infer the distinction from the word 'due' alone.

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