quickbooks_update_entity

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

Annotations already carry destructiveHint=true and readOnlyHint=false, and the description adds useful context: the effect parameter is a claimed read/write that Spring verifies, and approval_ref is needed when resuming a write. It also surfaces idempotency and governed-authority requirements beyond the structured annotations.

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 compact, front-loads the authoritative routing constraint, and organizes parameter explanations clearly in an Args list. It loses one point because the opening line is essentially redundant with the tool name and 'arguments' is described tautologically.

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?

An agent cannot reliably construct a correct call because it never learns what `arguments` should contain for a QuickBooks entity update, nor which entity types are valid. The infrastructure fields are well covered and an output schema exists, but the core domain operation is underspecified for a mutation tool with no required parameters.

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?

With 0% schema description coverage, the Args list compensates by explaining project_id, project_ref, connector_account_ref, idempotency_key, effect, and approval_ref. However, the central `arguments` parameter is only described as 'JSON string of arguments for the connector operation,' which is circular and leaves the actual update payload structure completely unspecified.

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 first sentence merely restates the operation name ('Quickbooks connector operation update_entity') and never states that this tool updates an existing QuickBooks entity or what kinds of entities are supported. The routing sentence and Args list describe infrastructure, not the tool's actual purpose.

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 guidance about when to use update_entity instead of quickbooks_create_entity, quickbooks_get_entity, or other update tools. 'Routes only through the exact project/account governed connector authority' is a routing constraint, not a when-to-use or alternative-selection instruction.

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