gorelo_list_time_entries

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

No annotations are present, so the description carries the disclosure burden. It does disclose pagination and optional filtering, but it omits response shape, ordering, default behavior with no filters, and any authorization requirements. This is moderate disclosure for a read-only-style list operation.

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?

Single sentence with no filler. The core action is front-loaded, followed by pagination and filtering details, and every phrase carries useful meaning.

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 14 optional parameters and no output schema, the description covers the essential list behavior, scope, pagination, and filtering intent. However, it does not describe the return value shape, ordering, or how filters interact, leaving meaningful gaps for an agent choosing how to construct a request.

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 descriptions cover only 8 of 14 parameters (57%), leaving the six array filter parameters undocumented in the schema. The description adds that filters 'narrow' results but does not clarify how multiple filters combine or their default semantics. Partial compensation for the schema gaps.

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 action and resource: 'List logged time' across tickets and tasks, which distinguishes it from sibling tools like gorelo_get_time_entry. The description also mentions pagination and filtering, making the operation clear.

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 'List... cursor-paginated... narrowed by any of the filters' phrasing implies a bulk retrieval use case, but there is no explicit guidance on when to use this tool versus gorelo_get_time_entry or other listing tools. No when-not-to-use or alternative routing is provided.

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