freshbooks_list_time_entries

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

The annotation readOnlyHint=true already covers the non-destructive nature. The description adds value by disclosing that the response envelope includes total_logged and total_unbilled, which is useful behavioral context about the return shape. This is comparable to the get_calls example where the description added scoping context beyond annotations.

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 two concise sentences with no filler. The primary action is front-loaded, and the extra response envelope detail is added without bloat. It is well-structured and efficient.

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?

There is no output schema, so the description must explain return values. It mentions total_logged and total_unbilled but does not describe the row structure, pagination behavior, or any edge cases. For a simple list tool this is adequate but leaves gaps, so a 3 is appropriate.

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%, and the description does not mention the page or per_page parameters at all. Since the schema provides only basic integer constraints and no descriptions, the tool description completely fails to compensate for this gap, leaving agents without any explanation of how pagination works.

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' and the resource 'tracked time entries', which is specific enough to distinguish it from other list tools like freshbooks_list_expenses. However, it does not explicitly differentiate itself from sibling list tools by name or contrast, so it falls short of a 5.

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 such as freshbooks_list_records or freshbooks_list_expenses. There is no mention of typical use cases, filtering, or exclusions, so an agent gets no help in choosing this tool over others.

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