get_timesheet

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: totals are preserved across pages and the continuation cursor must be followed. It stops short of explaining what a partial page looks like or how grouping affects the response shape.

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 dense sentence with the core operation front-loaded and no filler. The trailing pagination directive is terse but earned, though the grouping enum inline makes the sentence slightly hard to parse.

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 22-parameter, nested-object tool with 14% schema coverage, the description is far too thin; an output schema exists so return values needn't be explained, but most input parameters remain opaque. The pagination hint is the only compensating detail.

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 coverage is only 14% across 22 parameters, so the description carries a heavy burden it does not meet. It clarifies from/to and the group_by enum (0=none, 1=user, 2=card) but leaves detail, time_unit, time_precision, condition, only_general_sum, with_daily_distribution and the id-array filters entirely undocumented.

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 (Read) and resource (time tracking) scoped by date range and workspace filters, so the agent knows exactly what the tool returns. It does not, however, differentiate itself from close siblings like get_user_timelogs or get_card_timelogs, which cover overlapping ground.

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 explicit when-to-use guidance and no naming of alternatives, despite two near-duplicate siblings (get_user_timelogs, get_card_timelogs) in the toolset. The only directive, 'Preserve totals and follow continuation,' is about pagination mechanics rather than tool selection.

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