list_time_entries

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

The description discloses pagination behavior and the fetch_all parameter, which are not in annotations (none provided). However, it does not mention filtering capabilities via parameters, performance implications, or response format.

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: first clearly states purpose, second explains the critical fetch_all behavior. No fluff, front-loaded with the most important information.

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?

Despite having 16 parameters including many filters, the description fails to mention filtering, ordering, or output structure. As a list tool with pagination and no output schema, it lacks sufficient context for effective use.

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?

With 0% schema description coverage, the description adds minimal parameter information: only fetch_all is explained. It indirectly references user_id and workspace_id but leaves the other 14 parameters entirely undescribed.

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 clearly states the verb 'List', the resource 'time entries', and the scope 'a user's on the workspace', which distinguishes it from sibling tools like 'get_time_entry' for a single entry or 'list_expenses' for a different resource. The mention of pagination adds specificity.

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?

No guidance on when to use this tool versus alternatives like 'get_time_entry' for a single entry or other list tools. The description does not state prerequisites or conditions for use.

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