freshbooks_list_items

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

With readOnlyHint=true in annotations, the safety profile is already clear. The description adds useful behavioral details: supports pagination, passes raw FreshBooks filter params verbatim with no field validation, and returns page/pages/total. This goes beyond the annotation without contradicting it.

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 a single, compact sentence that front-loads the core purpose and includes only relevant details about pagination, filters, and return values. Every clause earns its place with no redundancy.

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 list tool with three optional parameters, one nested object, and no output schema, the description is sufficiently complete: it states the resource scope, return fields, and key behaviors. It does not cover error handling or rate limits, but these are not critical for a read-only list operation given the annotation and schema richness.

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%, so the schema already documents all three parameters (page, search, per_page) with examples and constraints. The description adds only general statements about pagination and raw filters, not specific parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('items for the authenticated FreshBooks account'), clearly distinguishing it from sibling list tools for invoices, projects, clients, etc. It also mentions the return payload (items plus page/pages/total), reinforcing the tool's purpose.

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 usage when a user needs to list items, but it does not explicitly state when to choose this over alternatives (e.g., get_item or list_invoices). The mention of pagination and raw filter params hints at use cases, but no exclusions or comparative guidance is provided.

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