clio_list_payments

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds context beyond that: it discloses a governed routing constraint ('Routes only through the exact project/account governed connector authority'), states that Spring verifies the effect must be 'read', and explains approval_ref exists for resuming writes. It does not contradict annotations, but it stops short of richer behavioral detail such as rejection behavior, rate limits, or pagination.

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 definition is compact and organized into a header, a routing constraint, and a parameter list, and the parameter list earns its place given the empty schema descriptions. However, the opening line is redundant, repeating the operation name twice ('Clio connector operation list_payments' and 'platform tool clio.list_payments'), and no sentence states the core behavior. It is efficient but not exemplary.

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?

The output schema and annotations cover return values and safety profile, reducing the burden on the description. Still, the description omits practical invocation contract details: what to place inside 'arguments', which of the routing parameters are required for a real call, and how to distinguish this tool from the many sibling payment-listing tools. Adequate for a low-complexity connector wrapper, but with clear gaps.

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 0%, so the description carries the full burden for parameter meaning. It provides a one-line semantic role for all seven parameters (payload, project UUID, correlation ref, account alias, idempotency key, effect constraint, approval context), which is genuinely useful. However, the most important parameter, 'arguments', is only described as 'JSON string of arguments for the connector operation' without any detail on what the Clio list_payments payload should actually contain.

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 only restates the operation name ('Clio connector operation `list_payments`') without ever explicitly stating that the tool returns payment records from Clio. The first line is essentially a tautology, and the only additional sentence concerns routing authority, not what the tool accomplishes. An agent must infer the purpose solely from the tool name.

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?

There is no statement of when to use this tool versus any alternative. Among the siblings are at least six other payment-listing tools (xero_list_payments, billcom_list_payments, freshbooks_list_payments, myob_list_payments, quickbooks_list_payments, square_list_payments), but the description gives no selection criteria, conditions, or exclusions. The routing note hints at scope but does not guide tool choice.

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