freshbooks_list_clients

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

Annotations declare readOnlyHint=true, so the safety profile is known. The description adds that it supports pagination and returns items plus page/pages/total, which is useful behavioral context beyond the structured metadata. It does not disclose rate limits or error behavior, but it is sufficient for a read-only listing tool.

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 three brief, front-loaded sentences with no redundancy. Every clause earns its place, covering purpose, pagination, and return shape efficiently.

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, the description covers the purpose, pagination, and return shape, while the schema handles parameter details. It lacks deeper context about the search object's behavior, but that is already in the schema, so the overall package is complete.

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 coverage is 100% with descriptive property definitions for page, search, and per_page. The description's mention of pagination and raw filter params mirrors the schema, adding no new semantics beyond what the property descriptions already provide.

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 clearly states the tool lists clients for the authenticated FreshBooks account with a specific verb and resource. It also mentions pagination and filters, distinguishing it from single-client retrieval tools like freshbooks_get_client.

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 use when needing multiple clients and mentions pagination/filter support, providing clear context. However, it does not explicitly contrast with sibling tools such as freshbooks_get_client or list other resources, so it stops short of full exclusions.

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