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

Annotations already indicate that this is a write operation (readOnlyHint: false) and potentially destructive (destructiveHint: true). The description adds no behavioral context beyond that—no mention of side effects, permission requirements, or what happens to existing data. With annotations present, the bar is lower, but the description still offers no added transparency.

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 concise—two sentences that front-load the purpose and define the term 'recurring transaction'. It is efficiently written with no wasted words, though it could benefit from more context without harming conciseness.

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 tool is complex (nested RecurringInfo structure, multiple fields), and there is no output schema. The description does not explain what the response looks like, what errors might occur, or any prerequisites (like company selection). The agent is left to infer behavior from the schema alone, which is insufficient for a create operation with this complexity.

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%, so the schema documents both parameters. However, the description adds valuable semantics beyond the schema: it provides a concrete example of the RecurringInfo structure and explicitly warns against sending sensitive data (SSN, tax IDs, birth dates, card-processing details). This enhances the agent's understanding of the entity parameter beyond the schema's generic description.

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 states a specific verb and resource ('Create a recurring transaction in QuickBooks Online') and further clarifies that it's a template used to create transactions on a schedule or on request. This clearly distinguishes it from sibling tools like create_invoice or create_bill, which create actual transactions rather than recurring templates.

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 description does not provide any guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or suggest when to prefer other create_* tools. The purpose is implicit but no explicit usage context is given.

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