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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: private notes and contractor pay rates are withheld by default, and include_private_notes must be set to surface them. It does not discuss pagination or rate limits, but the pagination contract is documented in the schema.

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?

Front-loaded with purpose, then filters, then the privacy caveat, then the endpoint. The long field enumeration is dense but justified because there is no output schema, so it is the only place response fields are described. No filler sentences.

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 and 15 optional parameters, the description compensates by naming the returned fields and the filter/privacy behavior. The remaining gaps (pagination flow, auth requirements, sort defaults) are either covered by the schema or only marginally relevant to a read-only list call.

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 73%, so the schema already documents most parameters (top, skip, sort, descending, date_from/date_to, invoice_id, activity_type, include_private_notes). The description restates the filterable dimensions and reinforces the privacy gating of include_private_notes, but adds no syntax, format, or default detail beyond the schema, and silently omits id, top, skip, sort and include_custom_fields. Baseline 3 is appropriate 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?

Specific verb ('List') plus resource ('time entries'), with an explicit enumeration of the fields returned and the dimensions available for filtering. It is trivially distinguishable from siblings such as bill4time_list_expenses or bill4time_list_invoices, and it names the backing endpoint (GET /timeEntries).

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?

It states the supported filter dimensions (client, project, user, invoice, entry date range, billing status) and a clear condition for include_private_notes ('unless include_private_notes is set'), which tells the agent when that flag matters. It stops short of explicit when-not guidance or naming an alternative tool, but among the list_* siblings there is little ambiguity to resolve.

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