freshbooks_list_items

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

Annotations already declare readOnlyHint=true and the description agrees by using 'List.' The description adds useful behavioral context beyond annotations by disclosing pagination support and the high-level response shape ('items plus page/pages/total'). No safety-relevant behavior is hidden.

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?

Three short sentences, front-loaded with the core purpose and no filler. Each sentence contributes either the action, the capabilities, or the return shape.

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 tool with fully documented parameters, the description covers authentication scope, pagination, filter capability, and the top-level return shape in the absence of an output schema. It could go further by describing the item object shape, but the essentials are present.

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 100%, and the description does not add meaning beyond it: pagination and raw FreshBooks filter params are already spelled out for page, per_page, and search. It correctly signals the three parameters exist but adds no new semantic detail.

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 opens with a specific verb and resource—'List items for the authenticated FreshBooks account'—so an agent knows exactly what operation this exposes. It does not explicitly differentiate from siblings like freshbooks_get_item, though the list-vs-get distinction is reasonably inferable from tool names.

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 gives clear context that this is the list-all/query endpoint with pagination and raw filter passthrough, so its use case is implied. However, it never names alternatives or exclusion criteria, such as using freshbooks_get_item when a single item is needed.

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