op_list_time_entries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds genuinely useful behavioral detail about the return format: both ISO-8601 duration and decimal hours plus a total, which helps the agent understand output without an output schema. This goes beyond what annotations provide.

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 short sentences with no fluff. The core purpose is front-loaded, and the second sentence adds practical value about the returned format. Every word earns its place.

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?

Given that this is a simple read-only list tool with a fully described schema and read-only annotations, the description is almost complete. It explains the key return-value detail that would otherwise be missing without an output schema. It does not mention pagination or default project behavior, but those are partially covered by parameter descriptions and are minor for this 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 all six parameters are already documented. The description does not add meaning beyond what the schema provides, but it also does not need to. It mentions no parameter-specific behavior, so the baseline of 3 is appropriate.

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 identifies the action ('List') and the resource ('logged time'). It is distinct enough from siblings like op_log_time (which creates time entries) and op_list_time_entry_activities (which lists activity types). However, it could more explicitly say 'time entries' and distinguish itself as the read-only listing sibling.

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 explicit guidance about when to use this tool versus alternatives, such as op_log_time for creating entries or op_list_time_entry_activities for activity types. The description simply states what it does without addressing selection criteria, filter combinations, or exclusions.

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