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

The annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to restate that this is a safe read operation. It adds useful domain context by explaining that a recurring transaction is a template used to create transactions on a schedule or on request, but it does not disclose error behavior, response shape, or any additional operational traits.

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 two sentences with no filler. The first sentence states exactly what the tool does, and the second briefly explains the domain concept in a way that helps the agent understand the resource. It is front-loaded and appropriately sized.

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 single-resource lookup with read-only annotations and fully documented parameters, the description is largely complete for selecting and invoking the tool. It does not explain return values, but that is not necessary for a straightforward get-by-Id operation, and no output schema exists to contradict that expectation.

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 input schema has 100% parameter description coverage, so the schema already documents id and company clearly. The description only confirms lookup 'by Id' and does not add further meaning beyond what the schema provides, which fits the baseline for high schema coverage.

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 a specific action ('Get a single recurring transaction'), names the resource ('from QuickBooks Online'), and identifies the lookup key ('by Id'). It does not explicitly distinguish itself from the sibling search_recurring_transactions, but the singular 'by Id' phrasing makes the intended use apparent.

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 usage context is implied: use this when you already have the QuickBooks Id and need exactly one recurring transaction. However, there is no explicit guidance about when to choose this tool over search_recurring_transactions, nor any mention of the optional company parameter requirement when multiple companies are connected.

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