list_time_entries

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

No annotations are present, so the description must fully disclose behavioral traits. It mentions filter_expr but omits important details about pagination (top, skip), sorting (orderby), field selection (select), default behaviors, or result limits. This is a significant gap for a listing tool.

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 concise at two sentences, but it sacrifices necessary detail. While no words are wasted, the brevity leads to incompleteness, so it is average.

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 has 5 parameters, numerous sibling tools, and an output schema, the description is insufficient. It lacks context about default pagination, sorting options, or how this tool complements or differs from other list_time_entries tools. The output schema exists but does not compensate for missing behavioral context.

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 coverage is 0%, meaning the description must explain all parameters. Only filter_expr is briefly described as 'OData filtering'. The other four parameters (top, skip, select, orderby) are completely undocumented in both schema and description.

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 'List time entries' which is a specific verb+resource. However, it does not differentiate from sibling tools like list_time_entries_for_client or list_time_entries_by_billing_status, which also list time entries with specific filters.

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?

The description only hints at using filter_expr for OData filtering but provides no guidance on when to use this general list vs. the many more specific list_time_entries_* siblings. No when-not-to-use or alternative suggestions are provided.

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