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

readOnlyHint=true already tells the agent this is a safe read, so the description needn't repeat safety. It adds "Paged", which is useful behavioral context beyond the annotation, but it doesn't say how filters combine (AND), what the default ordering is, or what the paging envelope looks like beyond the schema's next_page hint.

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 sentences, front-loaded with the purpose and then the filter axes, with zero filler. The trailing "Paged." is terse to the point of being a fragment, but it is still information-dense and appropriately sized for a list tool.

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 no output schema, the description could say more about what an entry contains or how pagination results are returned, and for an 11-parameter tool it doesn't mention sorting or filter combination behavior. It is nonetheless adequate to call the tool correctly, since the schema carries all parameter 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 description coverage is 100%, so all 11 parameters — including page, page_size, order_by/order_direction pairing, and the RFC 3339 bounds — are already documented in the schema. The description's filter list largely mirrors that, and it omits the sorting parameters entirely, so it adds little beyond the structured data.

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?

The description gives a specific verb and resource ("List tracked time entries") plus the filterable dimensions, which clearly separates it from the single-record get_time_entry or the write-side create_time_entry siblings. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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 enumeration of filters implies when this tool is appropriate (browsing/querying entries by project, user, billing state, etc.), but there is no explicit "use this instead of X" routing and no stated prerequisite such as needing a project_id or user_id first. An agent has to infer that this is the collection-level read versus papierkram_get_time_entry.

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