List Time Entries

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

No annotations provided, so the description carries the burden. It states that it returns individual entries plus a summary with total hours, which is helpful return context. However, it lacks details on pagination behavior, permissions, or rate limits. With zero annotation coverage, more behavioral detail would be expected, but the return format is a start.

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?

Three sentences, front-loaded with the action, followed by filtering options and return details. No wasted words, and the date format note is concise and useful.

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?

The description covers what the tool does, how to filter, and what it returns (entries plus summary). It doesn't explain pagination or sorting behavior, which are in the schema but could be relevant. Given no annotations and the presence of pagination parameters, adding pagination context would improve completeness, but overall it's sufficient for a list tool.

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 parameters are already well documented. The description adds only the date format for after and before, which is already in the schema descriptions. It doesn't add meaning beyond what the schema provides, but since schema does the heavy lifting, a 4 reflects that the description doesn't subtract value and clarifies the date filters.

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 (List) and resource (time entries) with the source system named. Clearly distinguishable from siblings like productive_log_time, which presumably creates entries.

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?

Describes filtering options but gives no explicit when-to-use guidance versus alternatives. Productive.io has other list tools and a log_time tool, yet the description doesn't say when to choose this list over other retrieval methods or when to avoid it.

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