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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the 'single ... by Id' scoping nuance; it says nothing about not-found behavior, required company disambiguation, or error conditions that a read-by-id tool would benefit from disclosing.

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?

A single front-loaded sentence with no padding; the verb+resource+scope lead is immediate. The trailing conditional clause is slightly awkwardly worded but still short and purposeful.

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 simple two-parameter read-by-id tool with annotations carrying the safety profile and no output schema, this is largely sufficient. Minor omission is the absence of not-found/empty-result behavior, which would round out an otherwise adequate definition.

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 100% and both parameters (id, company) are documented in the schema itself. The description's 'by Id' adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource with clear scope: fetch one RefundReceipt from QuickBooks Online by Id. It implicitly differentiates from the search/list siblings via the 'no search ... answer already holds it' clause, but never names search_refund_receipts, so the differentiation is inferential rather than explicit.

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 a when-condition ('when no search or write answer already holds it'), which is genuine usage guidance rather than none. However it is vague and refers abstractly to 'search or write answer' instead of naming search_refund_receipts or update_refund_receipt, leaving the agent to infer which sibling to prefer.

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