freshbooks_list_expenses

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

Beyond the readOnlyHint annotation, the description discloses a subtle edge case: if a total is reported with no rows, the count includes unreadable records and this is surfaced in a `note` field. It also reveals default ordering (newest-first) and support for raw filter syntax, adding significant 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 three sentences, front-loaded with purpose and key behavior. Every sentence adds value: listing purpose, pagination/filters, and the permission-related edge case. No unnecessary verbosity.

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 no output schema, the description covers the essential aspects: purpose, ordering, pagination, filter syntax, and a critical caveat about unreadable records. For a read-only list operation with three parameters, this is complete and self-sufficient.

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. It adds meaning to the `search` parameter with a concrete example ({"search[categoryid]": 5}) and explains pagination, but does not explicitly discuss `page` or `per_page` semantics beyond that. The pagination mention plus self-evident parameter names provide adequate compensation.

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 states 'List expenses for the account, newest-first by default', providing a specific verb (list), resource (expenses), and scope (account). This clearly distinguishes it from sibling tools like freshbooks_get_expense (single expense) and freshbooks_list_expense_categories (categories).

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 communicates clear context for use: listing expenses, with pagination and raw FreshBooks filters. However, it does not explicitly name alternatives (e.g., freshbooks_get_expense for a single expense) or exclusions, so it stops short of full when/when-not guidance.

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