update_transfer

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost none of it. It does not disclose that this is a mutating operation, that sync_token implements optimistic concurrency (a stale token will fail), whether omitted fields are preserved or cleared, what permissions are needed, or whether the change is reversible.

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?

It is a single front-loaded sentence with no padding, so nothing is wasted. But the brevity comes from under-specification rather than discipline—there is no second sentence adding the sync_token or field-mutability context a caller needs.

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?

This is a mutating tool with a nested parameter object, zero annotation coverage, and no output schema, which is the case where the description must do the most work. It supplies none of the missing context: update semantics, concurrency requirements, return value, or error conditions are all absent.

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 0% in substance: the nested properties carry only tautological labels such as "Transfer ID", "Sync token" and "Transfer amount". The description adds nothing beyond them, and critically never explains that sync_token must match the server's current value or that from_account_ref/to_account_ref define the money movement direction.

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 names a specific verb and resource ("Update a transfer") and adds the system context (QuickBooks Online), so the basic action is identifiable. However it stops there: it never says which transfer fields can be changed, whether it is a partial patch or a full replace, or how it differs from sibling mutations like update_deposit or update_journal_entry. The name is carrying most of the disambiguation.

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 no when-to-use guidance at all: no statement that an existing transfer id and current sync_token are prerequisites, no note to call get_transfer first to obtain the token, and no mention of create_transfer/search_transfers as the alternatives for other intents. An agent must infer the entire workflow from the schema.

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