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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description is not required to restate mutation semantics. It adds the requirement of Id and SyncToken, which is useful operational context. However, it does not mention the sparse-update behavior, the inability to delete employees (use Active: false), or the restriction on sending sensitive fields — those details live in the schema, not the description.

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 a single sentence that leads with the action and resource, then immediately gives the key prerequisite. There is no padding, and every word contributes to the agent's understanding of when and how to invoke the tool.

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 has a nested entity parameter and a high-complexity schema, and the annotation indicates destructive behavior. The description is minimal but does highlight the critical Id and SyncToken requirement. However, it omits the nuanced update semantics (sparse/full, restrictions on sensitive data, the Active: false retirement pattern) that are only found in the schema. While the schema enriches the definition, the description alone is not fully self-sufficient for this complexity level.

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%: both 'entity' and 'company' parameters have descriptive text. The tool description itself adds no parameter-specific semantics beyond the mention of Id and SyncToken, which is redundant with the schema. Per the baseline rule, a score of 3 is appropriate when the schema carries the descriptive weight.

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 the action ('Update') and the resource ('an existing employee in QuickBooks Online'), which immediately distinguishes it from create/delete/search operations on employees. It also adds the prerequisite requirement (Id and SyncToken), which further clarifies the scope of the operation.

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 implies usage by stating the action and prerequisite, but it does not explicitly compare against sibling tools like create_employee, get_employee, or search_employees. An agent would benefit from a direct when-to-use/alternative statement, and the brief description leaves that to inference.

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