list_time_entries

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral constraint: the read:time_entries permission scope. However, it omits pagination/result limits, what happens when start_date or end_date is null, and whether filters combine with AND semantics.

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. It is efficient, though its brevity is partly achieved by omitting information the agent needs rather than by tight editing.

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 six-parameter list tool with no annotations and no output schema, the description leaves most of the call contract undocumented. An agent cannot tell how results are ordered, whether they are paginated, or how the optional filters affect the response.

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 0% and six parameters exist, so the description must compensate; instead it only references the date range. Filters like user_id, project_id, billable, and include_active are left entirely unexplained, including what null defaults mean.

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 states a specific verb and resource ("List time entries") plus the scoping dimension (date range), so the agent knows exactly what operation this performs. It does not distinguish itself from related siblings like hours_by_day or get_hours_summary, which also surface time data.

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 guidance on when to choose this over hours_by_day or get_hours_summary, nor on required prerequisites beyond the scope. The date-range phrase only implies usage, and nothing is said about when-not to use it.

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