list_time_entries

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

No annotations are provided, so the description carries full burden but fails to disclose any behavioral traits. It doesn't indicate if this is a read-only operation, how results are returned (e.g., paginated), authentication requirements, rate limits, or error conditions. The description is too minimal to provide any useful behavioral context.

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?

The description is extremely concise with a single sentence, but this is due to under-specification rather than effective brevity. However, based on the scoring criteria for this dimension, it's front-loaded with zero wasted words, earning full points for conciseness despite lacking substance.

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 the tool's complexity (listing operation with pagination parameters) and lack of annotations, the description is incomplete. While an output schema exists (which reduces the need to explain return values), the description doesn't cover essential context like authentication, usage scenarios, or parameter meanings, leaving significant gaps for an AI agent.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'page' and 'per_page' mean in this context, how pagination works, default behaviors, or any other parameter semantics. The description fails to address the two undocumented parameters.

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 'List time entries' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this tool from its sibling 'list_' tools (like list_clients, list_projects) beyond the resource name, nor does it clarify what 'time entries' represent in this context.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (like authentication), context for listing time entries, or how this differs from other list operations (e.g., filtering capabilities or relation to create_time_entry).

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