freshbooks_list_clients

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the routing path and auth scopes (JWT, tenant, company), but does not specify whether the tool is read-only, what side effects exist, or what the response contains. The auth context is useful but incomplete.

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 (two sentences plus an args line) and front-loads the tool name and routing path. It is concise, but the content is of low informational value, focusing on routing rather than core functionality.

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 the existence of an output schema, the description does not need to detail return values, but it fails to provide a clear overview of what the tool does. For a list operation, it should at least indicate that it retrieves clients and provide behavioral context, which is missing.

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 only parameter 'arguments' is a JSON string with default '{}'. The description says it contains 'arguments for the connector operation', but does not specify what keys or structure are expected. With 0% schema description coverage, the description should compensate, but it provides insufficient guidance.

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 merely restates the tool name as 'Freshbooks connector operation `list_clients`' and provides routing details, but does not explicitly state what the tool does (e.g., retrieve a list of clients). The purpose is implied by the name, but the description adds no clarifying value.

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 given on when to use this tool versus sibling tools like freshbooks_list_expenses or freshbooks_list_invoices. There is no mention of prerequisites, context, or alternatives.

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