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

readOnlyHint=true already declares the safety profile, so the description only needs to add context such as pagination behavior, default ordering, or how filters interact — none of which it provides. The only added information is the REST endpoint, which is of marginal use to an agent selecting a tool.

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?

Two short sentences with the purpose front-loaded and no filler. The trailing 'API: GET /v1/time-entries' is arguably redundant for tool selection but is cheap and occasionally useful for cross-referencing documentation.

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 nine optional filters, cursor pagination, and no output schema, the description leaves the agent to infer how filters combine, what the default ordering is, and what a page of results contains. The schema carries the parameter burden, but the overall definition is only minimally adequate for a multi-filter list endpoint.

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%, and each of the nine parameters is documented in the schema with format examples (comma-separated ids, ISO-8601 timestamps, page_size 1-200). The description adds no semantics beyond that, so the baseline 3 applies.

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 logged time') plus the scope it spans ('across tickets and tasks'), so an agent knows it returns time-entry records rather than tickets or tasks themselves. It does not explicitly contrast with the sibling write tool gorelo_log_time_entry or with gorelo_list_project_tasks, but the verb+resource is unambiguous.

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 statement of when to use this tool versus alternatives, no mention of prerequisites, and no guidance on how the filters are meant to be combined. The agent must infer everything from the parameter names.

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