update_time_activity

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 it discloses almost nothing. It does not explain that this is a partial/sparse update requiring a sync_token for optimistic locking, whether omitted fields are preserved or cleared, what errors occur on a stale token, or what permissions are needed.

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 single sentence contains no filler and is easy to parse, so it is concise in the literal sense. But it is drastically under-sized for a nested-object mutation tool, and the one useful signal it could front-load — sync_token requirements — is absent.

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?

Given a nested params object, two required fields, a mutation with concurrency control, and no annotations or output schema, the description is far too thin to let an agent call this correctly. Only the resource identity is conveyed; everything about update semantics and field interactions is missing.

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 reported at 0%, and the description adds no meaning to any of the seven nested fields (id, sync_token, hours, minutes, item_ref, description, billable_status). It does not clarify the relationships between hours/minutes and the likely total-duration field, nor that sync_token must come from a prior read.

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 ("Update a time activity") and names the domain (QuickBooks Online), so an agent knows exactly which entity is being mutated. It does not, however, distinguish this from its siblings get_time_activity, delete_time_activity, or search_time_activities beyond the verb, and it never says what fields are updatable.

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, no prerequisites (such as needing an existing ID and current sync token), and no mention of the alternative siblings for reading or listing time activities. The agent must infer all routing decisions from the tool name alone.

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