freshbooks_list_time_entries

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

Annotations already declare readOnlyHint=true, and the description adds useful context about the response envelope containing total_logged and total_unbilled. This enriches the agent's understanding of the tool's output without contradicting 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?

Two concise sentences, front-loaded with the main purpose and a second sentence for the response envelope detail. 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?

For a simple read-only list tool with two optional pagination parameters, the description covers the core behavior and response envelope. The schema documents the parameter constraints, and the readOnlyHint covers safety. It could be more complete by explicitly stating pagination behavior, but the current coverage is adequate.

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?

The schema has no descriptions for the page and per_page parameters, and the description does not explain them. While the names are self-explanatory for pagination, the description adds no meaning beyond the schema's type and constraints.

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 tool lists tracked time entries for the business, using the specific verb 'List' and resource 'time entries.' This distinguishes it from sibling tools that list other entities (invoices, clients, projects).

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 implies the tool is for retrieving time entries, but provides no explicit guidance on when to use it over alternatives, such as create_time_entry or other list tools. Sibling names distinguish the resource, but the description itself doesn't state any exclusions or alternative contexts.

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