Retrieve a specific QuickBooks refund receipt by its unique ID to access detailed refund information.
Get a specific RefundReceipt record by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| refundReceiptId | Yes | The unique RefundReceipt ID |
Changes observed during successful MCP inspections.
v1.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry full burden. It only states 'Get ... record' implying read-only, but does not disclose any additional behavioral traits such as required permissions, error conditions, or return format. Insufficient for informing an AI agent.
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 a single, concise sentence of 10 words. It is front-loaded with the essential action and object. No extraneous information.
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 low complexity (one simple parameter, no output schema), the description is adequate but could be improved. It does not describe what is returned or any prerequisites. Passable but not fully 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 one parameter having a description. The description adds 'by its ID', which is redundant with the schema. Baseline 3 is appropriate as the schema already provides necessary detail.
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 retrieves a specific RefundReceipt record by its ID. The verb 'Get' and resource 'RefundReceipt record' are specific, and it distinguishes from sibling tools like qbo_refund_receipts_list or qbo_refund_receipts_create.
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 on when to use this tool versus alternatives. It does not specify that for multiple records one should use the list tool, or when to use create/update. The description offers no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.