freshbooks_list_payments

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

No annotations are provided, and the description only mentions routing and authentication details. It does not disclose whether the operation is safe, idempotent, paginated, or what happens when no payments exist. The behavioral characteristics beyond invocation are absent.

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 concise at 4 sentences but sacrifices informativeness. It is structured logically (name, routing, arguments) but does not earn its sentences with useful content for an AI agent.

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 explain return values, but it fails to reference it or provide any context about the data returned. The tool is simple, but the description lacks completeness for an agent to understand its scope and behavior.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' which adds minimal meaning over the schema type. With 0% schema description coverage, the description fails to specify expected keys or structure, leaving the agent without meaningful 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 tool name 'freshbooks_list_payments' clearly indicates the resource (payments) and action (list). The description identifies it as a Freshbooks connector operation for listing payments, distinguishing it from other Freshbooks list tools like 'freshbooks_list_clients' or 'freshbooks_list_invoices', though no further differentiation is provided.

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 provides no guidance on when to use this tool versus other list payments tools from different platforms (e.g., billcom_list_payments, stripe_list_payments) or alternative approaches. No context on filtering or prerequisites is given.

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