freshbooks_list_expenses

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

The description only mentions routing context (JWT, tenant, company scope) but omits critical behavioral traits such as read-only nature, pagination, performance implications, or result ordering. With no annotations, the description carries the full burden and fails to disclose key behaviors.

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 short but not refined; it wastes space on routing details that could be inferred from the platform. It is adequately structured with a header and args line, but lacks impactful content that earns each sentence.

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?

Despite having an output schema, the description does not mention what the tool returns (list of expense objects), nor does it address typical expectations for a list operation like filtering or sorting. The description is incomplete for practical use.

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 sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which is circular and uninformative. With 0% schema description coverage, the description should compensate by explaining the structure of the JSON or common options, but it does not.

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 restates the tool name ('list expenses') without clarifying the specific scope or differentiating it from siblings like freshbooks_list_invoices. It lacks a verb+resource structure that would uniquely identify the tool's purpose beyond the name.

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 other Freshbooks list operations (e.g., invoices, payments). The description does not mention any prerequisites, filters, or scenarios where list_expenses is appropriate.

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