quickbooks_list_credit_memos

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description only needs to add beyond that. It adds the governed-connector routing constraint and Spring's verification of `effect`, which is modest context. However, the 'approval_ref ... when resuming a write' note is irrelevant and potentially confusing for a read-only operation, though not a direct contradiction.

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 compact and organized: a lead line, a routing constraint, then a clearly separated argument list. It is not bloated, though several parameter descriptions are generic boilerplate rather than substantive guidance.

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 7-parameter connector wrapper, the description omits the core business behavior of listing credit memos and gives no operation-specific details such as filtering, pagination, or what should go into `arguments`. The output schema and annotations cover return shape and safety, but the description still lacks enough context to invoke the tool confidently beyond a trivial default call.

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?

Since the schema has no property descriptions, the description's argument list is the only parameter guidance. It provides basic labels for `project_id`, `connector_account_ref`, and `effect`, but the critical `arguments` parameter is left as a generic 'JSON string of arguments' with no operation-specific structure or example. This is partial compensation for the 0% schema coverage, but not sufficient for full clarity.

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 states 'Quickbooks connector operation `list_credit_memos`', which restates the tool name rather than explaining that it retrieves QuickBooks credit memos. It does not distinguish this from sibling list tools such as quickbooks_list_invoices or quickbooks_list_vendor_credits beyond the name itself.

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 only usage context is 'Routes only through the exact project/account governed connector authority', which is a routing constraint, not guidance on when to use this tool. No alternatives, exclusions, or conditions are mentioned, so an agent must infer applicability solely from the name.

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