freshbooks_list_expenses

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

Beyond the readOnlyHint annotation, the description adds meaningful behavioral details: default ordering, pagination support, raw filter syntax, and a subtle edge case where a total may include records the identity cannot read, surfaced via the note field. This is valuable transparency.

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 focused sentences. The first states the core purpose and ordering; the second covers pagination, filters, and an important caveat. Every sentence 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 read-only list operation with three optional parameters and no output schema, the description covers the key behaviors: ordering, filters, pagination, and the unreadable-count caveat. It is slightly incomplete in not detailing page/per_page semantics or naming alternatives, but it is largely 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?

The schema has 0% description coverage, so the description must compensate. It mentions 'pagination' and gives an example of a raw filter, but it does not explain the individual page or per_page properties, their defaults, or how they interact. This is only partial 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 a specific verb and resource ('List expenses for the account') and adds ordering ('newest-first by default'). It clearly distinguishes this from sibling tools like get_expense or create_expense by framing it as a list operation.

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 provides context but gives no explicit guidance on when to choose this tool over alternatives such as get_expense or create_expense. There is no mention of when not to use it or what conditions favor a sibling tool, leaving the agent to infer usage.

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