List Time Entries

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

With no annotations, the description carries the full burden, and it only discloses that pagination exists and filters are optional. It never states the read-only nature explicitly, nor auth requirements, defaults, or rate limits. An output schema exists, so return-value detail is fairly excused, but the behavioral picture remains thin.

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 sentence with no padding or repetition. The trailing "with optional filters and pagination" is slightly generic but still earns its place by naming the two operative dimensions.

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 an 8-parameter list tool with full schema coverage and an output schema, the essentials for invocation are present. However, the fetch_all pagination behavior and the read-only nature are never surfaced at the description level, leaving the agent to reconstruct usage from structured fields alone.

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% across all 8 parameters, so limit, offset, fetch_all, and every filter are already documented in the schema. The description adds no syntax, format, or interaction detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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 time entries") and notes the two axes it operates on, filters and pagination. It implicitly distinguishes itself from the singular sibling get_time_entry, but never names or contrasts with it explicitly, so differentiation is left to inference.

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, no prerequisites, and no mention of the pagination-vs-fetch_all tradeoff that the schema flags for reports/aggregations. "Optional filters and pagination" describes what the tool does, not when an agent should choose it over get_time_entry or search.

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