list_time_entries

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

With no annotations at all, the description carries the full behavioral burden, yet it only signals implicitly that this is a read operation. It says nothing about pagination defaults, result ordering, permissions needed, or what happens when limit is exceeded — all relevant for a list tool with 6 optional params.

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 filler; every word earns its place. It is arguably too terse given the missing behavioral detail, but it is not padded or disorganized.

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 list tool with no annotations and no output schema, the description should explain default result scope, pagination behavior, and rough return shape. None of that is present, leaving significant gaps for an agent to infer.

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%, so every parameter (from/to, limit, user_id, issue_id, project_id) is already documented in the schema including formats and defaults. The description only restates the filter dimensions without adding format, default, or interaction details beyond the schema.

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 clear verb and resource (list time entries) and names the filterable dimensions. It implicitly distinguishes the read operation from siblings like log_time, update_time_entry, and delete_time_entry, though it doesn't call out the contrast explicitly.

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 word 'optionally' implies all entries are returned when no filters are given, which is useful usage context. However, there is no explicit when-to-use guidance, no mention of alternatives (e.g., for a single entry or for aggregations), and no stated prerequisites.

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